Deployment doesn't works in other machine

[Anish G]

Hi,

I am having an issue with the deployment. I created msi(vb.net project) setup file using .net setup project. The application works fine if I deploy it in my machine (where I created the setup file).

However, I tried to deploy the project in another machine. The installation goes fine and I didn’t got any errors while installing. But, when I open the application, the application window open and closes immediately. Not sure why this happens.

Any help?

[bplacker]

I had a problem with this also; my problem came about because the .Net framework was not installed on the other machine, and this caused major problems.

[Anish G]

I had a problem with this also; my problem came about because the .Net framework was not installed on the other machine, and this caused major problems.

Thanks for you reply.

I checked, .net framework is installed in that machine. Intially I created the setup file a month back, and it was working fine in that machine. Yesteraday, i did some changes in source code and re-created the setup file. As I said earlier this setup file deployment works in my machine but doesnt work in other machine(deploym ent goes without any error, but application window closes immediately when I open).

Any idea...?

[bplacker]

maybe try rebuilding the solution again, and re-deploying it. Maybe some error occured during the build process.

[Anish G]

maybe try rebuilding the solution again, and re-deploying it. Maybe some error occured during the build process.

Hi,

I found another issue. I copied the whole application (Not the setup file) to another machine and run the application from there. The application complies without any error but when I run that, the application window opens and closes immediately.

This happens only other machines, in my machine it works fine.

Also, when I add a setup project to my application (Add—>New Project), near the Setup file, there is tool tip saying “Not under User Control” with a yellow color plus sign.

Any idea why this happens in other machines, where as it works in my machine?

[Anish G]

Hi again,

I got the following error when i put a break point while running the application in another machine.

*Entering break mode failed for the following reason: Source file 'C:\Documents and Settings\Admini strator\Desktop \Coding app\Coding Tools\SharedCom ponents\UiThrea dCaller\UiThrea dCaller.cs' does not belong to the project being debugged.

Usually, this condition occurs when the project was not rebuilt prior to starting the debugging session, when the assembly file for the project is out of date, or when the project source files were moved to a different disk location between the time the project was built and the debugging session was started.

Edit and Continue will be disabled for this debugging session.*

The source file path(Source file 'C:\Documents and Settings\Admini strator\Desktop \Coding app\Coding Tools\SharedCom ponents\UiThrea dCaller\UiThrea dCaller.cs') mentioned here is my machine path(machine where the application was running). As per the Message, I rebuilt the application. But still no luck.

Please help me.

[kenobewan]

Are there any differences between the machines - OS, ASP.NET or IIS? Suggests something is different about the setup of the two machines.

[bplacker]

'C:\Documents and Settings\Admini strator\Desktop \Coding app\Coding Tools\SharedCom ponents\UiThrea dCaller\UiThrea dCall er.cs'

does this path exist on the second machine you moved to?

Try Publishing the application, then copying the produced setup file to a second machine, and running it from here. I had much difficulty with creating setup files, etc... and found this path much easier to take for the time being. You just go to Build -> Publish