deployment - VB.NET: Can the .EXE built by VS2005 be deployed as a standalone EXE? -

-

VB.NET: created by VS 2005 .exe as a standalone Can be deployed to EXE ?

When I change the mode in "Release" in VS2005 and create the solution, then the solution in the bin \ release directory is .exe File, but this is also the .pdb , vshost.exe and .xml file. What are these additional files and what are they necessary?

I copied the file to another machine and it was executed properly, but after that there was a significant delay in executing for the first time. It was like any other program, what is the reason for this, and can it be helped? Is it because the other 3 files in the release folder are not there?

itemprop = "text">

The project template you used to start the project is not very optimal settings as a result you will find clutter It can be easily fixed, start with Project + Property, compile tabs. Make sure the release build is selected, the upper left combo box is the configuration label.

  • The .pdb file contains debugging symbols. You do not need it for release build, although you receive a little more informative exception messages. Stack trace will include line numbers on them Can not rely on the release build, click the advanced compiling option, debug info = do not generate any.

  • The .xml file contains intellisense information, when you use the XML documentation in your source code, the meaning of being used for the referenced assemblies in another project, an EXE project Absolutely random for Close the "Generate XML Documentation File" option on the compile tab.

  • The .vshost.exe file is an assisted process for debugging your app, to configure it separately with security issues during debugging, a custom version of this CLR Hosts. It also produces the console. WrightLine () appears in the Visual Studio Output window. For the release build, there is a small issue in keeping the Debug tab and unchecking the "Enable Visual Studio Hosting Process" option.

After these changes and rebuilding, you should only leave the .exe file in the bin \ release folder.

What is slow startup? NET Framework is called "cold start" of assemblies. This is due to the slow or broken hard drive as DLLs were never loaded earlier, so disk drives need to dig through GAC to find files. You can do better by defraging the disk. Cold start starts at the same speed as it starts.

A classic trick used by Microsoft Office and Adobe Acrobat, to load the file system cache by loading your DLL at the log time. They are called "adapter" in the startup folder or run the registry key. Very worried BTW, they slow down other programs. You can do the same thing by writing your small NIT program which does nothing, but makes some classes. Place a shortcut for it in the startup folder.


Comments

Post a Comment