deployment problem

[Injun]

I installed my app on another test machine with the same operating system it bombed giving me the error

"Application generated an exception that could not be handled ....click Ok to terminate....etc"

When I clicked cancel to debug , it gave me an error message "Registered JIT is not available.......etc"

I do use the infragistics Ultrawingrid controls and built in crystal reports.
Any idea what caused the problem?

I have not added any merge-module because I dont see one for the ultragrid . I checked for a merge module name on the infragistics website and could not find one.

Any help appreciated.

 

[chiph]

Possibly dumb questions:
1. Is the .NET framework installed on the other machine?
2. Did you install your 3rd aprty controls on the other machine?

Chip H.


____________________________________________________________________
Click here to learn Ways to help with Tsunami Relief
If you want to get the best response to a question, please read FAQ222-2244 first

 

[Injun]

I do have the .Net frame work on the other machine. I have version 1.0 and 1.1 intalled.

I didnt install the 3rd party control separately but the setup packaged the dlls and installed the dlls in the app directory.

Still I am getting this unhandled exception error

 

[mdwg2020]

Injun,

I don't know if you monitor often, but this is the exact same problem that I am having with my application. I saw your post RiverGuy, I am actually using ODBC to a SQL Server, and I have installed MDAC 2.7. I have no idea why the program throws an exception on the load, it has to occur when I am loading data, just as Injun was having the problem. I also have Framework 1.1 installed, and the app works perfect on development pc.

What exactly is going on with this?

 

[jubble]

Don't think this is the root of the problem but just in case...

I've also had problems with UltraWinGrid controls which stemmed from updating controls that already exist in the application.
Make sure your deployment project includes all the controls necessary, for example I had an app with WinGrid and others and then 6 months later added WinChart. The deployment project didn't even pick it up. It had to be added manually.

Also check the version numbers of your dll's.

How do you create your deployment project? In a seperate solution or the same solution as the app? From experience it's much more practical and VS.Net seems to pick up 3rd party controls more consistently in deployment projects that are in the same solution as the application.

 

[mdwg2020]

Hey Jubble,

I don't really have any 3rd party controls, but I did package my application with a setup project that was in the same solution. The thing is that when I physically install the application on my development PC everything is fine, so that would seem to me that possible something is missing in the package somehow. I have the .NET framework, doesn't that contain any of the missing pieces that the application my need?

I also downloaded the SDK on that PC and was going to attempt to build the solution but was having problems. I have Crystal Report objects within the solution, and its possible that these are causing the problems, but I'm not sure. They are physically part of the solution, so they should be built-into the application.

I'm lost, and this is very important to have done, not sure what is going on. Are there settings for the project properties or solution properties that could cause problems. Such as setting everything for debug or release, or clicking the build check box. I wasn't very familiar with all of those different options.

 

[jubble]

Firstly, don't forget MDAC 2.7.

Basically your dev machine has some components installed that your other machine is missing so barring an install of VS.Net(not recommended - it's nice to have two dev machines sometimes but when it comes to testing, these sort of issues never come to light until the client rings up to tell you he's binned your installation CD); you need to pinpoint the missing components

Crystal Reports is probably your problem. The best place to start is to go through all the references in all the projects in your solution and make sure that the corresponding dll's are in your setup project. If they're not then you have to manually add them.

If you don't have a complicated deployment package then I would recommend scrapping your current deployment package (remove it from solution and delete it from your drive just to make sure there's no lingering components that might get picked up if you use the same name) and start a brand new one.
Often this workaround 'Refresh' will automatically pick up the components that were overlooked before. Don't ask me why because it doesn't make sense to me either, but it's just one of those issues I've come across a couple of times. Some of the other guys here might be able to shed light on the behaviour.

 

[ThatRickGuy]

Also note that to deploy CR you need to drop the dotnetcrystalreports.msm and add the license.msm, reportengine.msm, VC_CRT.msm, and VC_STL.msm. For any machine that doesn't have CR installed.

-Rick

----------------------
If you're about to post an ASP.Net question,
please don't do it in the VB.Net forum

http://www.ringdev.com

I believe in killer coding ninja monkeys.

 

[mdwg2020]

Rick,

I simply created an entire new solution, and created the files all over again, so that it would pick up the references. Now my program says that it is adding crystal_managed2003.msm, so is this the one I should remove and add all of the ones that you suggested.

I'm also not sure how to do that. All I get is a list of dependencies, but it doesn't allow me to change them. How do I go about doing that?

Jubble,

I did install MDAC 2.7 so that shouldn't be my issue. So the references that are in the actual project that contains my application, are not automatically added to the setup? If that is true, sorry again for all the questions, but how do I add those .dlls to the actual setup program?

I thought using the setup wizard to create a quick setup actually picked up everything that you needed, but apparently that isn't true.

Thanks again guys for all of your help, you will be lifesavers as soon as all of this is over. I have now realized that I have a lot to learn about this deployment portion of VS.NET.

 

[ThatRickGuy]

I'm also not sure how to do that. All I get is a list of dependencies, but it doesn't allow me to change them. How do I go about doing that?

You're going to have to hit the BusinessDecisions(Crystal Reports) website, they have some good documentation on how to do it and the files needed. If I remember right it was like a 20+ meg download (bleh!). You'll need a license to deploy also.

-Rick

----------------------
If you're about to post an ASP.Net question,
please don't do it in the VB.Net forum

http://www.ringdev.com

I believe in killer coding ninja monkeys.

 

[mdwg2020]

Hey guys,

I told you guys would save my life. Thanks for all of the help. I just went through an install on another PC and it went great. Now I am going to package everything so that I can bootstrap the MDAC install as well as the Framework.

Again, thanks, you hit the nail on the head with the Crystal merge modules. There were quite a bit that I had to install.

It jumped my install from 860kb to about 9MB, but it worked. I will let you know if my bootstrapper works as well.

This is the reason that I come here, so many experts with so much knowledge.

Thanks again,

Brooks

 

[jubble]

but how do I add those .dlls to the actual setup program?

First go to the setup project
If the File System folder is not showing then click on the icon at the top of solution explorer named "File System Editor"
Right click "Application Folder" (if that's where you want the dll's)
Select Add file
Get all the dll's in your bin directory that are not already detected.

You can also use the option Add assembly but often it easier to select add file then go to your bin directory and that gives you a good picture of what should be in your setup package.

Note that sometimes not all the components are in your bin directory so you still need to ensure that all your project references have corresponding dll's in the setup package.

I thought using the setup wizard to create a quick setup actually picked up everything that you needed

It should and MOST OF THE TIME it does but I think it also depends on how the components were installed into the GAC, so it's not all VS.Net's fault. I've noticed that problems I've had with components always seem to be the same problems with the same components but haven't got to the bottom of it yet.

 

[mdwg2020]

Thanks Jubble,

I actually got it taken care of an bootstrapped the framework and MDAC components.

Brooks