How to prevent VB .NET from deploying my source code?

Hi everyone,

(This is probably a really dumb question, but I figure that there's an easy answer that I don't know. )

Using VB .NET 2003...simplest case, one developer, no source control, creating deployment packages to be installed on individual computers.

I just realized that the deployment package, in addition to setting everything up so the program will run, is also putting my source code in the executables directory where it is being installed. How do I prevent deploying my source?

For the record, my edition of VB .NET does not include the setup wizard, which has the option for whether or not to deploy source code readily available. I'm using the Setup Project Template and I can't figure out how to set it within there.

Thanks,
Bill

Is your project a release build?

Once you get your problem with including source files straightened out, you should consider that a .net executable can easily be decompiled to source code. There are products out there that can prevent this: http://www.remotesoft.com/salamander/protector.html

If I understand the terminology correctly, yes, it is a release build. I have release numbers and product codes and all that in there in the properties for the setup project. I just can't find the darn switch so as not to include the source code. :mad:

As for decompiling the executables back into source code, that's not a concern. If the users have that much time on their hands, more power to them. Rather, I just don't want the source out there as an attractive nuisance.

As for decompiling the executables back into source code, that's not a concern. If the users have that much time on their hands, more power to them. Rather, I just don't want the source out there as an attractive nuisance.

It doesn't take any time. Open a product like Reflector and the source is right there.

http://www.aisto.com/roeder/dotnet/

Figured it out. There was an entry in the Setup project for "Source Files from your application (Active)". I got rid of that and it resolved this issue.

Of course, it begs the question of why I didn't notice something so obvious until today, but I'm not going to look a gift horse in the mouth.