VB.NET deployed app will not run.
I am new to VB.NET, having moved from VB 6.0 finally. I imported a VB 6.0 app into VS 2008 and then opened it in VS2013, since the latter does not provide for importing VB 6.0 apps. Then, following the instructions at https://msdn.microsoft.com/en-US/library/k3bb4tfd(v=vs.80).aspx, I created a deployment/setup project with no problem. I then installed the project onto a target machine with no problem. But, when I launch the app following the install, I just get a pop-up dialog that says "<app name> has stopped running.". That's it, nothing more, and no forms of the app ever appear, not is there any evidence that the app ever started.
When I install the same build onto my dev machine it works fine. Also I have written another app (written, not imported from 6.0), and the setup project installs and runs fine on the same target machine noted above.
I really do not want to rewrite the app since it is pretty large.
When I install the same build onto my dev machine it works fine. Also I have written another app (written, not imported from 6.0), and the setup project installs and runs fine on the same target machine noted above.
I really do not want to rewrite the app since it is pretty large.
ASKER
Yes, It runs within the IDE as well as from the setup/install.
are you using a 3rd party components or some VB6 controls that are not included in your setup package?
ASKER
I am using ComponentOne controls as well as Crystal report viewing, but those references appear to be now included in VS. And, since the install runs fine on the DE machine, I would think that the deployment must have included everything it needs.
This is surely the problem. It is running on your Dev machine because you have installed the components on it. You better ensure by looking at the deployment package if those are included.
ASKER
Where do I look to see what should be included, and where do I include the from once they have been identified?
I assume you have downloaded Crystal for VS2013.
From the same place you downloaded Crystal you should be able to download the runtimes.
mlmcc
From the same place you downloaded Crystal you should be able to download the runtimes.
mlmcc
ASKER
I didn't download anything. I just used the component references included within VS. Am I supposed to download something and do a separate install on the target machine?
How did you get Crystal for VS2013?
mlmcc
mlmcc
crystal reports needs to be installed on the PC using the MSI (or MSM) provided by SAP. Check http://scn.sap.com/docs/DOC-7824
as for your ComponentOne controls, are they VB6 ocx or .Net DLLs? They also need to be included.
ASKER
I suppose I am quite confused. If I imported the VB 6.0 project into VS 2008 using the Upgrade Wizard, and the resulting project runs fine (after correcting all the errors of course), I would assume that the Upgrade Wizard would have made the necessary upgrades/replacements to the required components. So, now that appears to be incorrect. Also I forgot to mention that I installed the app on another IDE machine used by another IT person, and the app runs fine - and that machine does not have Crystal loaded, since he does not use Crystal.
ASKER
Eric:
The .NET .dlls are included, but the upgrade wizard also included a number of .ocx references.
The .NET .dlls are included, but the upgrade wizard also included a number of .ocx references.
the upgrade wizard does no magic. It can replace the VB6 textbox with the .Net textbox but it has no clue about Component One controls. All it can do is to create a wrapper around the .ocx and use them in .Net. That means that when you publish your application, you need to deploy the .Net Framework but also all the VB6 controls (as you did when installing your VB6 application) and the VB6 runtime.
>>and that machine does not have Crystal loaded, since he does not use Crystal
Try to run a report on that machine and you will see errors. CR needs to be installed.
>>and that machine does not have Crystal loaded, since he does not use Crystal
Try to run a report on that machine and you will see errors. CR needs to be installed.
>>but the upgrade wizard also included a number of .ocx references.
These needs to be deployed and registered as well.
These needs to be deployed and registered as well.
ASKER
Can I include a Crystal installer/.msi with the project like is done with InstallShied for example. If so, where do I get it and how do I tell the project to include it?
again, crystal reports needs to be installed on the PC using the MSI (or MSM) provided by SAP. Check http://scn.sap.com/docs/DOC-7824
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What version of Crystal do you have?
mlmcc
mlmcc
ASKER
I had come to the conclusion that rewriting the app was probably going to have to happen. The VS 2008 conversion wizard was intriguing as an easy way out, but as with most things in life - nothing is free.
Any error message?