Deployment

[Yuriy Galanter]

I have heard a lot that an application developed in VS.NET can be
deployed by simple Xcopying it to a target machine. But how do I deploy it
in reality? I've built a VB.NET project, now what do I do to deploy it to
another machine running .NET SDK? Speaking of which, does the target machine
has to have a full blown SDK or there is some run-time only option?

Yuriy Galanter

[Patrice Scribe]

The redistirbutable package is available from :

http://msdn.microsoft.com/downloads/.../sample.asp?ur
l=/msdn-files/027/000/976/msdncompositedoc.xml

Of course it's probably better to use a machine you could reinstall...

Patrice


"Yuriy Galanter" <yuri@galanter.net> a écrit dans le message news:
3b66ca17$1@news.devx.com...
> I have heard a lot that an application developed in VS.NET can be
> deployed by simple Xcopying it to a target machine. But how do I deploy it
> in reality? I've built a VB.NET project, now what do I do to deploy it to
> another machine running .NET SDK? Speaking of which, does the target
machine
> has to have a full blown SDK or there is some run-time only option?
>
> Yuriy Galanter
>
>

[Yuriy Galanter]

Thanks, got it. But what about deployment? I assume it's not enough
simple to copy content of the \bin folder onto the target machine?

Yuri.

"Patrice Scribe" <scribe@chez.com> wrote in message
news:3b683b74$1@news.devx.com...
> The redistirbutable package is available from :
>
>
http://msdn.microsoft.com/downloads/.../sample.asp?ur
> l=/msdn-files/027/000/976/msdncompositedoc.xml
>
> Of course it's probably better to use a machine you could reinstall...
>
> Patrice
>
>
> "Yuriy Galanter" <yuri@galanter.net> a écrit dans le message news:
> 3b66ca17$1@news.devx.com...
> > I have heard a lot that an application developed in VS.NET can be
> > deployed by simple Xcopying it to a target machine. But how do I deploy
it
> > in reality? I've built a VB.NET project, now what do I do to deploy it
to
> > another machine running .NET SDK? Speaking of which, does the target
> machine
> > has to have a full blown SDK or there is some run-time only option?
> >
> > Yuriy Galanter
> >
> >
>
>

[JT]

It is that simple provided you are not using anything in the GAC. All you
need is to copy your assembly and any other "non-System" assemblies into a
directory on the machine. That is it. Nothing more, nothing less. If you
are using the GAC, then you need to write a batch file that will install
assemblies you need into the GAC.

Kinda cool, isn't it?

JT
"Yuriy Galanter" <yuri@galanter.net> wrote in message
news:3b684ed1$1@news.devx.com...
> Thanks, got it. But what about deployment? I assume it's not enough
> simple to copy content of the \bin folder onto the target machine?
>
> Yuri.
>
> "Patrice Scribe" <scribe@chez.com> wrote in message
> news:3b683b74$1@news.devx.com...
> > The redistirbutable package is available from :
> >
> >
>
http://msdn.microsoft.com/downloads/.../sample.asp?ur
> > l=/msdn-files/027/000/976/msdncompositedoc.xml
> >
> > Of course it's probably better to use a machine you could reinstall...
> >
> > Patrice
> >
> >
> > "Yuriy Galanter" <yuri@galanter.net> a écrit dans le message news:
> > 3b66ca17$1@news.devx.com...
> > > I have heard a lot that an application developed in VS.NET can be
> > > deployed by simple Xcopying it to a target machine. But how do I
deploy
> it
> > > in reality? I've built a VB.NET project, now what do I do to deploy it
> to
> > > another machine running .NET SDK? Speaking of which, does the target
> > machine
> > > has to have a full blown SDK or there is some run-time only option?
> > >
> > > Yuriy Galanter
> > >
> > >
> >
> >
>
>

[Rob Teixeira]

In this case, you'll also need a key to provide strong naming for your project
and might also need a digital certificate depending on the type of project.
Working with GAC drives me as nuts as working with the registry, though I
must admit it is a *lot* easier.
On the other hand, if you don't need a global assembly, XCOPY install rules.
Of course, if your project depends on pre-.NET COM components, you will need
to install those as usual.

-Rob

"JT" <johntperry@hotmail.com> wrote:
>It is that simple provided you are not using anything in the GAC. All you
>need is to copy your assembly and any other "non-System" assemblies into
a
>directory on the machine. That is it. Nothing more, nothing less. If
you
>are using the GAC, then you need to write a batch file that will install
>assemblies you need into the GAC.
>
>Kinda cool, isn't it?
>
>JT
>"Yuriy Galanter" <yuri@galanter.net> wrote in message
>news:3b684ed1$1@news.devx.com...
>> Thanks, got it. But what about deployment? I assume it's not enough
>> simple to copy content of the \bin folder onto the target machine?
>>
>> Yuri.
>>
>> "Patrice Scribe" <scribe@chez.com> wrote in message
>> news:3b683b74$1@news.devx.com...
>> > The redistirbutable package is available from :
>> >
>> >
>>
>http://msdn.microsoft.com/downloads/.../sample.asp?ur
>> > l=/msdn-files/027/000/976/msdncompositedoc.xml
>> >
>> > Of course it's probably better to use a machine you could reinstall...
>> >
>> > Patrice
>> >
>> >
>> > "Yuriy Galanter" <yuri@galanter.net> a écrit dans le message news:
>> > 3b66ca17$1@news.devx.com...
>> > > I have heard a lot that an application developed in VS.NET can
be
>> > > deployed by simple Xcopying it to a target machine. But how do I
>deploy
>> it
>> > > in reality? I've built a VB.NET project, now what do I do to deploy
it
>> to
>> > > another machine running .NET SDK? Speaking of which, does the target
>> > machine
>> > > has to have a full blown SDK or there is some run-time only option?
>> > >
>> > > Yuriy Galanter
>> > >
>> > >
>> >
>> >
>>
>>
>
>