silly vb .net question...

[Troy]

I know this question may seem very silly, but I'm going to pose it anyhow.
I'm very new to VB.NET programming and just completed my first form-based
project. In previous VB versions, there was a "Make .exe" choice in the
File menu. There isn't anymore!? How does one simply convery their project
into an exe file? I would think this is an easy task, but I can't figure
it out for the life of me.

Thanks for any help,

Troy

[PWilmarth]

Well, it's kind of a subtle little issue.

Are you using Visual Studio? If you are, take a look at the Configuration
Manager under the Build Menu. You have 2 options to use when you compile
and Build your project Debug and Release. If you are building your project
under Debug, then look in the Debug folder of your Project. You will see
that it is already compiled as an exe (or dll, depending on what you are
doing). You'll find the exe (or dll) under the Release folder if you have
your Configuration Manager set to Release. Now if you want to deploy your
application, that's an entirely different matter.

[Troy]

Thanks much for the quick response PW. I do see the .exe file in the release
folder, and it will run from there. Yet, when I try and copy and paste it
to a location on my office network, it won't run without errors. Is that
what you were referring to when you said "deployment is an entirely different
matter."??

Does anyone know an easy way to move these executables onto a LAN?

Thanks...Troy

"PWilmarth" <pwilmarth80231@msn.com> wrote:
>
>Well, it's kind of a subtle little issue.
>
>Are you using Visual Studio? If you are, take a look at the Configuration
>Manager under the Build Menu. You have 2 options to use when you compile
>and Build your project Debug and Release. If you are building your project
>under Debug, then look in the Debug folder of your Project. You will see
>that it is already compiled as an exe (or dll, depending on what you are
>doing). You'll find the exe (or dll) under the Release folder if you have
>your Configuration Manager set to Release. Now if you want to deploy your
>application, that's an entirely different matter.

[PWilmarth]

Yes, I did.

I've only seen this covered in a couple of places. There's a fairly good
walkthrough on MSDN

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vbtskcreatinginstallerforyourapplication.asp

that can guide you through the process.

[Jeff Johnson]

"Troy" <troyg@logs.com> wrote:
>
>Thanks much for the quick response PW. I do see the .exe file in the release
>folder, and it will run from there. Yet, when I try and copy and paste
it
>to a location on my office network, it won't run without errors. Is that
>what you were referring to when you said "deployment is an entirely different
>matter."??

I've had no problems with the "XCopy install"-- IF the user's have .Net (w/
sp2) installed.

The trick I use to get it to work is to put any .dll's my project references
(and any graphics files, etc.) in the same folder as the exe-- both when
I'm writing the app and when I distribute it.

I'm not sure if this is what you're "supposed" to do or not... but I like
working this way...