running a .Net app from the network on a PC

that doesn't have any .Net framework installed on it.

I wrote an application that reads text files and Excel spreadsheets for input, and then produces a .txt file for the final report. It does not access any databases nor does it have any forms requiring connection or data adapter objects. I've placed it on the network so that the employees of the department can run this program from this location, rather than having me install in everywhere. On both the server and numerous employee PCs, I have gone into Control Panel -> Administrative Tools -> Microsoft .Net Framework Wizards to set the assembly at "Full Trust". However, when any employee double-clicks on the executable file to run it, they get this error message:

".NET Framework Initialization Error

C:\\Windows\\Microsoft.NET\\Framework\\v1.1.4322\\mscorwks.dll could not be loaded"

I have spoken to the department's director, and he has made it extremely clear that he will not purchase any software to get around this problem.

Can anyone offer any solutions on how I can make this program run from the network share location without having to install any .NET software onto every individual PC?

I think you need to install the client .DLLs on each PC that tries to run the application.

It seems stupid for a .NET framework to not be runnable over the network, doesn't it?

I think the way that it should work is that all the .net DLLs and so forth that are pointed to in various places in the Registry on the local computer, instead point to the various DLLs on a server somewhere. But unless HKEY_CLASSES_ROOT\\CLSID\\{04B1A7E3-4379-39D2-B003-57AF524D9AC5} and so forth can take [link|http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmc.doc/ans60000122.htm|UNC Names], and I don't think they can, then I think you're out of luck.

Why can't you put the .net DLLs on the clients that want to run your application? I would assume that a relatively simple installer script could check the registry for the presence of the .net framework and spawn the .net installer if it's absent. Alternatively, your application could probably be ported to Python pretty easily as there are Python modules to read .xls files.

Note that I'm not a programmer so the previous suggestions are left as an exercise for those who are.

HTH a bit. Good luck!

Cheers,
Scott.

Post #253,392 by lincoln 4/25/06 4:37:56 PM Reply	running a .Net app from the network on a PC that doesn't have any .Net framework installed on it. I wrote an application that reads text files and Excel spreadsheets for input, and then produces a .txt file for the final report. It does not access any databases nor does it have any forms requiring connection or data adapter objects. I've placed it on the network so that the employees of the department can run this program from this location, rather than having me install in everywhere. On both the server and numerous employee PCs, I have gone into Control Panel -> Administrative Tools -> Microsoft .Net Framework Wizards to set the assembly at "Full Trust". However, when any employee double-clicks on the executable file to run it, they get this error message: ".NET Framework Initialization Error C:\\Windows\\Microsoft.NET\\Framework\\v1.1.4322\\mscorwks.dll could not be loaded" I have spoken to the department's director, and he has made it extremely clear that he will not purchase any software to get around this problem. Can anyone offer any solutions on how I can make this program run from the network share location without having to install any .NET software onto every individual PC? lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]
Post #253,406 by inthane-chan 4/25/06 5:17:58 PM Reply	I'd be surprised if it could be done.
Post #253,417 by tonytib 4/25/06 6:15:47 PM Reply	Sounds correct, but at least .NET framework is free download
Post #253,439 by ben_tilly 4/25/06 11:22:02 PM Reply	Might be possible The trick with Perl is to install it to a network drive, then copy PerlCRT.dll from your system folder to the bin directory on the network drive. After that on any machine you can just add that bin directory to your PATH and then run Perl. You may be able to do something similar with .NET. However I'd suspect that you'd have a lot of network traffic if anyone actually used this setup... Cheers, Ben I have come to believe that idealism without discipline is a quick road to disaster, while discipline without idealism is pointless. -- Aaron Ward (my brother)
Post #253,440 by Another Scott 4/25/06 11:58:08 PM Reply	I doubt it. I think you need to install the client .DLLs on each PC that tries to run the application. It seems stupid for a .NET framework to not be runnable over the network, doesn't it? I think the way that it *should* work is that all the .net DLLs and so forth that are pointed to in various places in the Registry on the local computer, instead point to the various DLLs on a server somewhere. But unless HKEY_CLASSES_ROOT\\CLSID\\{04B1A7E3-4379-39D2-B003-57AF524D9AC5} and so forth can take [link\|http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmc.doc/ans60000122.htm\|UNC Names], and I don't think they can, then I think you're out of luck. Why can't you put the .net DLLs on the clients that want to run your application? I would assume that a relatively simple installer script could check the registry for the presence of the .net framework and spawn the .net installer if it's absent. Alternatively, your application could probably be ported to Python pretty easily as there are Python modules to read .xls files. Note that I'm not a programmer so the previous suggestions are left as an exercise for those who are. HTH a bit. Good luck! Cheers, Scott.
Post #253,468 by jb4 4/26/06 9:55:12 AM Reply	ICLRPD (new thread) Created as new thread #253467 titled [link\|/forums/render/content/show?contentid=253467\|ICLRPD] jb4 "Every Republican who wants to defend Bush on [the expansion of Presidential powers], should be forced to say, 'I wouldn't hesitate to see President Hillary Rodham Clinton have the same authority'." — an unidentified letter writer to Newsweek on the expansion of executive powers under the Bush administration
Post #253,490 by lincoln 4/26/06 3:24:59 PM Reply	Here's the solution On a test machine, I went to [link\|http://msdn.microsoft.com/netframework/downloads/framework1_1redist/\|http://msdn.microsoft.com/netframework/downloads/framework1_1redist/] and downloaded the free redistributable 1.1 framework file, 23 Meg in size, and then ran the install. Overall it took around 3 minutes. After that, we were able to run my program on that PC. So I copied the 23 Meg file to a network share so that others can copy it to their PCs and run the install. Now, if I can just get them as enthusiastic to download & install Service Pack 1 for the redistributable framework ... lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]
Post #253,572 by altmann 4/27/06 12:04:44 AM Reply	Windows Update will offer the SP once .Net is installed -- Chris Altmann
Post #253,622 by lincoln 4/27/06 11:25:32 AM Reply	Our jack-of-all-trades sysadmin restricts the updates that we get - he doesn't allow MS to shove just anything down our throats. Minimizes the headaches he'd potentially face the next morning after updates occur. lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]

Welcome to IWETHEY!