• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 771
  • Last Modified:

VB.net "Portable App"

Hello,

We need to develop a basic VB.net app for distribution to 100+ computers on a network.  We cannot assume the user has admin rights to their PC.  We can be sure that .NET will be installed.

How would we create a "Portable" version of our app, not requiring an install on the client's PC, but just an .exe that would launch immediately.  

Like I said, we can assume they already have .NET installed.

Thanks
0
compsol1993
Asked:
compsol1993
1 Solution
 
Luis PérezSoftware Architect in .NetCommented:
From what I know, if you're sure that right .Net Framework is installed, you can run your .exe without any problem.
0
 
Éric MoreauSenior .Net ConsultantCommented:
if the correct version of the .Net framework is installed (along with the correct SP), your application will run even if not "installed" if all other requirements (like additional 3rd party components) are available.
0
 
compsol1993Author Commented:
Ok, I guess that would be the problem, the 3rd party components/references -- is there anyway to package them all up into an .exe?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Éric MoreauSenior .Net ConsultantCommented:
no but you can copy them into the same folder as the .exe. normally, you take everything that is in the bin folder and copy it to the user's computer
0
 
Mike TomlinsonMiddle School Assistant TeacherCommented:
If you're looking for a "zero footprint" EXE based on a .Net application, including 3rd party components, then you'd have to shell out some $$$ for something like ThinApp:
http://www.vmware.com/products/thinapp/

That would allow you to embed the 3rd party DLLs (and the applicable .Net framework portions itself) INSIDE the EXE making it "stand alone".  With that tool, you wouldn't even need the .Net framework on the target machine.

*Of course you are sacrificing file size in the process...
0
 
grayeCommented:
I'd suggest that you just create a location on a network share, and but the *.exe plus all of it's required DLL files into that directory.

Then you could just tell folks to go to that network share (such as \\SomeServer\SomeShare\SomeDir\Some.exe).   You could create a shortcut for them... or they could just navigate to the correct location and double-click on the *.exe file.

This way, you'd end up installing (er, well... just doing a copy) the application "just once" on a network drive.   Nothing needs to be installed on the individual PCs at all (unless you wanted to install a shortcut on their desktop).
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now