How to disable warnings in Visual Studio for a Visual Basic Web Deployment Project

Question

For our VB.NET websites we use SVN for Source Control and CruiseControl.NET for continuous integration.

To use the SVN build number in the compilation by CruiseControl.NET we need to use Web Deployment Projects. We then replace in the configuration file the Version field with this variable from SVN Labeller

• $(CCNetLabel)

This works great but my problem is that this variable causes warnings in Visual Studio for the solution. I'm working to remove all warnings and am left with just these two:

• Warning 1 The version string specified for 'AssemblyFileVersion' in the project file is invalid. C:\MyProject\MyProjectDeploy.wdproj
• Warning 1 The version string specified for 'AssemblyVersion' in the project file is invalid. C:\MyProject\MyProjectDeploy.wdproj

I have searched for ways to disable certain warnings but they all reference Windows projects not web site/deployment projects which do not contain a Compile tab.

I found information on using #pragma warning( disable : 1000 ) but it appears this is for C++ only and not VB.

It's not a show-stopper but is annoying the hell out of me this lazy Friday afternoon, any help would be appreciated - if reputation sharing was working yet I'd offer someone 20 of my rep for a workable solution :) at least....

Answer 1

It is possible to ignore errors, it is just in a weird place for vb.net.

Open the .vbproj file with notepad or an equivalent and find the <NoWarn> tag and add the id of the error there.

in a default 2008 winforms, I have these warnings already ignored.

<NoWarn>42016,41999,42017,42018,42019,42032,42036,42020,42021,42022</NoWarn>

Answer 2

If you used Nant in your build script you could just have it re-write the version prior to compile, and you wouldn't see the warning when you are working on your local machines.

Answer 3

Had a very similar situation with an old VB web project, and we did not want to add the #pragma blocks all over the code calls. For some reason, adding the lines to the <NoWarn> fields did not make Visual Studio builds ignore/suppress the warnings.

However, I found a different approach. By adding this in the .vbproj file after the <NoWarn></NoWarn> area ignored the obsolete warnings in VS 2017: <DisabledWarnings>612;618</DisabledWarnings>

Common MSBuild project properties Description of configuration setting:

DisabledWarnings Suppresses the specified warnings. Only the numeric part of the warning identifier must be specified. Multiple warnings are separated by semicolons. This parameter corresponds to the /nowarn switch of the vbc.exe compiler.