Shaitan00 Posted July 27, 2007 Posted July 27, 2007 Not sure if this is normal or not but I created a deployment project for my tool (tool.exe) which was created using VSC# 2003 .Net 1.1 and after running the MSI (installing) there is a tool.exe.config file that also appears (I can also see it in primary outputs of the deployment project). If I delete the file after install the tool.exe still runs fine and I see no reason to keep it (I kind of liked that it was a one-file deployment) so I wanted to know a few things: - Is there a reason to keep this file post-install? - Is there a way to remove it from the outputs of my MSI package (deployment package)? Because I don't recall ever adding it before and I don't see anywhere I can remove it from the outputs of the project... Any information or help would be much appreciated... Thanks, Quote
Administrators PlausiblyDamp Posted July 28, 2007 Administrators Posted July 28, 2007 (edited) Have you added an app.config to the project - if so that is what will end up as the tool.exe.config. In a nutshell the .exe.config file is simply a configuration file for the associated application, if it isn't present then any configuration it contains will not be available to the exe. Out of interest what does the .config file contain? Edited August 31, 2007 by PlausiblyDamp Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.