Visual studio 2013 installshield source code files not compiled and all code exposed after installation

Question

0.00/5 (No votes)

See more:

VS2013

I used Visual Studio 2013 and InstallShield Limited Edition to make an install exe file for my Windows Form program. But when I install it on my own computer, and then, in the installation directory(e.g. "C:\\Program Files (x86)\AppName\"), all .cs files are not compiled and can be opened with notepad and all my source code is there! How do I stop .cs files from showing itself?

Screenshot of Installation Directory

What I have tried:

I have absolutely no idea how to do this. I did a lot of searching, but with no avail.

Posted 28-Sep-17 22:47pm

WhatsYourIdea

Updated 29-Sep-17 2:14am

Richard MacCutchan

v3

Add a Solution

Comments

Richard MacCutchan 29-Sep-17 5:13am

It sounds like your InstallShield script is set to package all the source code of your project instead of the executable. I suggest you check your setup parameters.

WhatsYourIdea 29-Sep-17 6:51am

How do I access the InstallShield Limited Edition setup parameters in Visual Studio?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Answer 1 · 2017-09-29T02:14:00

You have probably selected the wrong files to be packed in your setup executable.

See Simple Steps to Create Setup File Using InstallShield LE From VS 2012[^] for a step-by-step guide. It is for VS 2012 but should cover VS 2013 too.

See there Step 4: Application Files. If there are no special dependencies, just activate the Add Project Outputs button and select Primary output.