Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 12-14-2005, 05:08 PM
jmm jmm is online now
Registered User
 
Join Date: 07-29-2004
Posts: 10
CF.NET barfs on AssemblyFileVersionAttribute

I have a CF.NET solution (smart device project) that I wish to have VBP version stamp. Ideally, in the same method VBP is used to version-stamp the rest of our win32 software.

VBP is adding the 'AssemblyFileVersionAttribute' in the AssemblyInfo.cs files, but this class is not supported in the compact framework. Why is VBP adding that attribute rather than simply modifying 'AssemblyVersion'? (I know that the latter approach works for both .NET & CF.NET.) Is this a VBP bug? Is there something we are doing wrong?

FWIW, the .bld file used to build *all* .NET projects looks like:
<?xml version='1.0'?>
<project version='5'>
<step action='Make VS.NET' type='0'>
<Attr type='11'>-1</Attr>
<Config>%CONFIG%</Config>
<FileVer type='11'>-1</FileVer>
<Filename>%PROJ_FILE%</Filename>
<ParseOutput type='11'>-1</ParseOutput>
<ShowCmd type='11'>-1</ShowCmd>
<Version>%BLDVERSION%</Version>
<VersionSel type='3'>2</VersionSel>
<indent type='3'>1</indent>
<name>Build VS.NET</name>
</step>
</project>
Reply With Quote
  #2  
Old 12-14-2005, 05:34 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
http://www.visualbuild.com/Manual/?vsnetversiontab.htm:
"Only the Assembly and Product versions apply for Smart Device (Compact Framework) projects; the File version option should be unchecked for these project types."
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 06:24 AM.


Copyright © 1999-2023 Kinook Software, Inc.