Can somebody please tell me where I can find info on distributing the applications I create with VB.NET 2005 Express
I have looked around and a lot of sites say that there isn't a facility to do this but I have got the "Publish" button.
I need a complete guide so that everything works - did a little test and sent the setup.exe to a friend but he couldn't use it. Brought up an error. Can somebody help Thanks in advance,

Distributing Applications
UlliDK
Thanks for the info SJ...
But would it be possible if I just put the .exe on a fileserver to execute it directly from the fileserver and use no setup routine at all The corporate LAN is pretty fast.
Thanks again,
DLLnewbie
Roger, you can single space your lines by not pressing the enter key each time you type in a line: the editor will automatically wordwrap the lines. If it's frustrating for you, it's
also
frustrating
for
us!
p.s. If I need to spell check, copy your whole entry into Word and see what errors it comes up with. Or simply use the preview button and re-read what you typed (it's a failing that we all have - just hitting the post button without proof-reading).
Additionally, I personally find the default font size too small to read - I'll select the 'smaller' (
) font size to make is slightly bigger (it shows correctly in preview). I also prefer Verdana as a font for reading rather than Tahoma (but I don't like green eggs and ham).
As far as distribution of applications go, I prefer the free versions: specifically, NSIS. Although harder to use (it's a scripting/command line application which can create a nice graphical installer), it really forces you to think about what you are doing.
Also, if your application doesn't use any funky controls or assemblies, and the .NET 2.0 framework is installed on the client computer, you can simply copy the application and run it: no 'install' required.
(edit to add): ClickOnce is a nice technology. However, the express edition is very limited (justifyably so). The 'upgraded' versions are much more powerful. But, the complexity of ClickOnce is not because of the technology, but because installation is a very complex issue - and one that many software developers and distributors get completely wrong (they underestimate the energy needed to develop a reliable install/uninstall scenario). This is one reason where I advocate a 'manual' installer initially for developers (Such as NSIS or Inno). Get it right there, and you appreciate what is needed for an installation, and you will use the cool tools (ClickOnce) much more effectively.
Ken Porter
mywoong
Depending on your policy, you may run into security exceptions when running from a share.
Check out http://blogs.msdn.com/shawnfa/archive/2003/06/20/57023.aspx.
Best regards,
Johan Stenberg
Susan_MSFT
Thanks for the info...
How about signing - do I have to sign the ClickOnce things to be able to set up the application I create on another PC And how do I do this - can't make much sense of the MSDN link above.
Thanks,
mma01
SJWhiteley,
Thanks for the info...
The application will sit on a fileserver and run from client machines - I don't need a fancy installer program because it will only be for my company that I'm producing this software for. I wanted to see if I could actually use the thing before forking out for the full version. Would it just be the .exe in the Debug/Build directory that I'd need to use then (plus any .dll's etc.)
Thanks again,
P.S. Roger G,
If you do want to start a new line, hold <shift> then press <enter> and it will only do a single line, not double. Same as in Microsoft Frontpage.
DonBaechtel
VB Express supports ClickOnce deployment. Check out
http://msdn.microsoft.com/smartclient/understanding/windowsforms/2.0/features/clickonce.aspx
and
http://msdn2.microsoft.com/en-us/library/t71a733d.aspx
for more information.
Best regards,
Johan Stenberg
Josh K....
Theoretically, yes: if you build your application, it creates an EXE (in the Bin/Release folder), then all they should need is that executable.
However, noone should need a 'fancy installer'
. Particularly for a single EXE. However, the installer can be effectively a silent installer:
Or even just copy the exe to an installed location (such as Program Files/CompanyApps/My App, or c:\MyAppHere). I'm not sure if clickOnce actually cmpresses the file, but most installers also include some kind of compression algorithm (I know, I know, you're on a LAN, but how many times have you heard people complain that the network is slow, for whatever reason Don't be part of the problem
)
All of this is pretty close to what ClickOnce does. Indeed, If you only have a single EXE, the ClickOnce works. Sort of.
However, by doing it manually, you can control almost everything about the install, it won't need the 'installer runtime', you'll be able to register and unregister DLLs, check serial numbers, etc, etc. Sure, it's work on your part, but presumably you are writing programs to make someone elses life easier, not necessarily yours (and I wish a few more programmers would realize that
).
ClickOnce works. I've tried it several times (and actually it has a nice Roll Back feature). I haven't tried the 'upgraded' (Standard/Pro) version, yet.
Mark_E475
I agree that if you have visions of you'r software sitting on
the shelves at BEST BUY, then you should spend the Money
for the real deal. I was following the step by step example in
the guided tour for Click Once when I did something wrong
and I went off on my weird tangent. I was happy to just get the
program to install so it wouldn't seem like a waste of time to
spend days writeing a program that I couldn't use anywhere
but the computer I wrote it on. Although my Wife thinks it's all
a waste of time. I don't care as I'm retired and just a novice
or hobbyist as it said when I found VB Express. I'm not impressed
with those web sites either. They just seem to say what you can
do with Click Once and they don't give a here's how you do it
for dummies. I can't even get this text editor to single space the
lines. The best I can say is to use the example in the guided tour.
I did't see any thing about haveing to sign in there. One More
comment about Click Once, I have slower than Molasses in
January Internet out here in the sticks and I wouldn't be happy
if I bought a program that I had to wait 2 1/2 hours for it to
download the.NET Framework 2. Otherwise I really like the
Express Editions. They keep me from Total boredom through
the winter. I had toyed around with Liberty Basic some but didn't
know if I wanted to spend the money on Upgrading from the
limited edition or buy Visual Basic or C++. This has solved that
problem and it didn't cost me anything except all the books I've
been buying as of late.
Roger G.
Ps. I wish this thing had a spell checker.
vsk
I was very confused also,especially about the Prerequisites.
I came up with this cobbled up way of getting it on a windows
98. I found the dotnetfx redistributable somewhere when surfing
around and downloaded it along with the windows installer 3.1
I found somewhwere else. You can search for them on MSDN.
Anyway this is probably not the Most effient way but it worked.
You will have to download the .NET framework redistributable,
"dotnetfx" and include it on the cd.
To install Program
A.
1. Click Start then control panel and double click Add/Remove Programs.
2. check to see if .NET Framework 2 is there . If it is then go to C.
If not then go to B.
B.
1. Open My Computer and double click your CD ROM drive where the
installation disc is .
2. Make sure you are connected to the internet and double click the dotnetfx
in your cd drive. This should install .NET Framework 2.
C.
1. Click start then run and browse . Browse to the CD ROM drive where your
disc is and open it.
2. Double click The exe. file.( the one with no numbers after it.)
3. Click OK on the run box and the program should install.
I saw a post yesterday about adding the redistributables into your solution.
I tried it and they showed up in the application file in the solution publish
propertys and also in the deploy files after I published it. I haven't tried it
yet as I don't want to remove everything from the other computer and start
all over yet.
an
Chinni
Mukilan
It's a case of 'suck it and see': what happens if you do that (I'm guessing it won't let you, actually - it'll probably crash out with an exception).