I've religiously filled out all the info in the My Project\AssemblyInfo.vb and hardcoded the version number as 3.1.0.12 for instance. I build/rebuild and go to the newly built AppName.exe assembly and right click and look at properties and no version tab and no version info even in the Summary\Advanced section....what am i missing here TIA Harry
Do you have VS2005 Service Pack 1? The latest .NETCF Service Pack? I remember there was a bug which affected Visual Basic .exe .NETCF v2.0 projects only and would not build in the version resource. It didn't affect C# projects or VB.NET class library projects). I think it was fixed in the service pack for Visual Studio. Peter -- Peter Foot Microsoft Device Application Development MVP www.peterfoot.net | www.inthehand.com In The Hand Ltd - .NET Solutions for Mobility "Harry Simpson" wrote in message news:%23OvSwm03HHA.2108@TK2MSFTNGP02.phx.gbl... > I've religiously filled out all the info in the My Project\AssemblyInfo.vb > and hardcoded the version number as 3.1.0.12 for instance. I > build/rebuild and go to the newly built AppName.exe assembly and right > click and look at properties and no version tab and no version info even > in the Summary\Advanced section....what am i missing here > > TIA > Harry >
Thanks Peter, I think I've got the VS2005 w/ SP1 installed. I did need to install VS2003 AFTER I installed VS2005 - wonder if that boogered anything. My about box for VS2005 reads v 8.0.50727.762 (SP.050727-7600) ..NET Framework is v.2.0.50727 Shouldn't the SP1 update the CF 2 for me? I do have weird behavior when I double click on a solution file it says this was created with a more recent version of Visual Studio and I just drag the solution file over to my VS2005 icon shortcut and it opens just fine. Maybe reinstalling SP1 is recommended? Thanks!! Harry "Peter Foot [MVP]" wrote in message news:4772650A-34A6-43D2-9ABB-BB5569E5A5CE@microsoft.com... > Do you have VS2005 Service Pack 1? The latest .NETCF Service Pack? I > remember there was a bug which affected Visual Basic .exe .NETCF v2.0 > projects only and would not build in the version resource. It didn't > affect C# projects or VB.NET class library projects). I think it was fixed > in the service pack for Visual Studio. > > Peter > > -- > Peter Foot > Microsoft Device Application Development MVP > www.peterfoot.net | www.inthehand.com > In The Hand Ltd - .NET Solutions for Mobility > > "Harry Simpson" wrote in message > news:%23OvSwm03HHA.2108@TK2MSFTNGP02.phx.gbl... >> I've religiously filled out all the info in the My >> Project\AssemblyInfo.vb and hardcoded the version number as 3.1.0.12 for >> instance. I build/rebuild and go to the newly built AppName.exe assembly >> and right click and look at properties and no version tab and no version >> info even in the Summary\Advanced section....what am i missing here >> >> TIA >> Harry >> >
Reinstalled VS2005 SP1 and that did clear up the 2005 sln not being associated with VS2005 IDE But it did not clear up the problem of the assembly info not being transfered to the EXE file info - when you right click a file and select properties. I'm used to seeing a version tab with all the assemply info but no assembly info exists here. When I right click the project in the IDE and select properties, then select the Assembly Information button all the info from AssemblyInfo.vb appears just fine. Any ideas how to get that info into the compiled exe's metadata? TIA Harry "Harry Simpson" wrote in message news:%23OvSwm03HHA.2108@TK2MSFTNGP02.phx.gbl... > I've religiously filled out all the info in the My Project\AssemblyInfo.vb > and hardcoded the version number as 3.1.0.12 for instance. I > build/rebuild and go to the newly built AppName.exe assembly and right > click and look at properties and no version tab and no version info even > in the Summary\Advanced section....what am i missing here > > TIA > Harry >
