Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have some .msm merge modules (for Crystal Reports if you must know) that I want to convert to one single .msi installer package. I can do this with a Visual Studio setup project, but then I cannot avoid a requirement for .Net being included in the package.
Perhaps for my reputation it is better to delete this question, but just in case there are more nutheads like me:
The Setup project creates two files: the setup.exe and the myapp.msi.
Setup.exe will install .Net whatever you do, but if you run the .msi and you are sure no dependecies on .Net exist, it will not demand a .Net framework installation…
I am now going to get drunk…