Printable View
I have writting a few .net applications that both work fine when I try to execute them from my c drive.. however if i try to execute them from a network drive they won't run...
Any ideas on what I need to do to let them run on the network drive..
(btw I have run other (non .net) executables from the network drive.)
You need to set permissions.
Quote:
Originally posted by DevGrp
You need to set permissions.
Could you go further into that for me? I appologize for my ignorance, but don't know what you mean, or how to do it.
Try running the caspol utility(c:\winnt\Microsoft.NET\Framework\v1.0.3705). This should allow applications to run over share points.
caspol -s off.
Hope this helps
Harold Hoffman
Thanks Harold that fixed it... on my machine...
Now i have run into a new problem:
My program run fine on machines that have VS installed, but give an error on machines that only have the Framework installed.
Any ideas??
those machines have the .netframework on them the other ones dont you need to install the .net framework on the other machines
It is installed on the machines in question.Quote:
Originally posted by robdotnet00
those machines have the .netframework on them the other ones dont you need to install the .net framework on the other machines
So:
It works on the machines with VS.NET
It does NOT work on the machines that have
.NET Framework and no VS.NET
"Application has generated an exeption that could not be handled.
Proces id =0x474 (1140), Thred id=0x518 (1304).
Click OK to terminate the application
Click CANCEL to debug the application."
This message appears even with the .NET Framework installed.... It does *NOT* appear on the machines that have VS.net
Any Ideas?
maybe you have included some component that you did not distrubute like crystal reports.net ?
Quote:
Originally posted by robdotnet00
maybe you have included some component that you did not distrubute like crystal reports.net ?
That makes sense... I have included adodb.net ... I can't think of anything else a few COM references, however these machines would have all the COM stuff I included...
Do I have to do anything special to distribute adodb?
How do I go about distributing those controls?
I believe all of that stuff should be included in the .net framework. Have you created the windows installer package for your app. That should gaurentee that you are distrubuting everything u need to be distrubuting.
Quote:
Originally posted by robdotnet00
I believe all of that stuff should be included in the .net framework. Have you created the windows installer package for your app. That should gaurentee that you are distrubuting everything u need to be distrubuting.
To tell you the truth I have never tried to play with the windows installer.... I don't even know where to find it...
Is it trivial to use?
btw: thank you very much for your help the last few messages... i appreciate it!
I dont think it is too difficult to use but i have only played with it im sure you can find a tutorial it can be found in one of the projects in vs.net but i dont recall which one off hand.
Just to make clear:
- the computer sharing the executable should not have .Net installed (you can even put it in a IIS virtual directory and run the exe from the internet - there are strict permissions on this kind of execution, but it's great for fat clients over the internet)
- the computer running the exe should only have the framework installed. The exe assembly should contain all .Net objects. You need to be carefull with COM interop. You're back in DLL hell. And that won't run... without some work.
Try building an install package that inckludes the COM components you're using. The user will have to install the program before executing it (yes... like the good old days) to register the COM's.
Maybe there is a compiler option to include DLL's or OCX's in the assembly? Anyone know?
Also check for compiler options to switch between DEBUG/RELEASE (it's possible that debug requires VS on the computer) or options that tell the compiler to include "everything".
Hope this helps!
When you create an installer project via the VS wizard it will generate all the dependancies it finds in the main project.
It can arrange registering off COM dlls.
You must ensure .NET dlls you added which were additional to standard .NET framework (1.0 or 1.1? I guess they all have same but you could check this) are included in the installation.
Your addition .NET dlls can be copied into the bin of your app so they are local to that app only. IF you need them to be in the GAC then they need to be stong named - but you don't need to put them in there.
IF you know all the dlls needed you can do all this manually simply by copying them to the client machine (obviously COM dlls always need to registered in the trad way).
Sometimes you may have used a component only to remove it but has it been removed from the referenced assemblies?
Oh BTW -
doesn't caspol -s switch off all security checking of dll's in .NET for everything on the machine? Is this really wise???