View previous topic :: View next topic |
Author |
Message |
grr
Joined: 18 Sep 2011 Posts: 11
|
Posted: Sun Jan 29, 2012 7:59 am Post subject: Warning MSB3042 |
|
|
Hi
Just embedded the new ILS Source within an App VS2008 VB.Net Win7.
On a build it reports:
C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.VisualBasic.targets : warning MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "AuthenticatedLicenseInstallForm.vb". This may lead to an incorrect choice for the manifest resource name for resource "AuthenticatedLicenseInstallForm.resx".
AND
C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.VisualBasic.targets : warning MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "EvaluationDialog.vb". This may lead to an incorrect choice for the manifest resource name for resource "EvaluationDialog.resx".
Is this normal?
Have I stuffed up something?
Should I just ignore the warning?
Regards...
grr |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sun Jan 29, 2012 11:00 pm Post subject: |
|
|
This warning is normal - unfortunately VB.NET doesn't provide any way to turn off warnings. The warning is caused by the conditional code blocks around the form class definitions which define the classes to be public or private. When the classes are defined in the Infralution.Licensing assembly they need to be public so that your application can be referenced. When you include them in your application then you probably want them to be private so they can be obfuscated (if you are using an obfuscator)
If you want to get rid of the warnings you can simply remove the conditional blocks and declare the classes as private. _________________ Infralution Support |
|
Back to top |
|
|
grr
Joined: 18 Sep 2011 Posts: 11
|
Posted: Mon Jan 30, 2012 9:34 am Post subject: |
|
|
Obfuscators do not really work very well and cause an extra burden on the developer and the final assembly.
I searched for ages to find a better solution and this was the infralution .Net encryptor.
It is really fantastic and allows me to secure my app in a reasonable and non-intrusive way.
With this in mind would you suggest to ignore the warnings or remove the conditional blocks and declare the classes as private. I don't really care about the warnings, just want some informed advice on best practice.
Regards...
grr |
|
Back to top |
|
|
|