updating an application

[Saso Zagoranski]

Hi!

I have developed an application which I'm about to distribute to my clients.
It's a pretty big project so bugs are sure to be found somewhere along the
line or updates will be needed.
What I would like to know is how are patches for applications are made.
I wouldn't like to send .dll files to clients and ask them to copy the files
in their install dir.
I've heard about versioning for assemblies, where you just send a new
assembly, which
has a higher version number? How can you then specify which assembly should
be used?

Thanks,
saso

[Saso Zagoranski]

Re: updating an application

That means that instead of referencing the assemblies in VS.net I would
have to manually load them at runtime?
How can I then access then access the classes from that assembly...
assembly.class?
So "using" can't be used anymore? I would have to change quite a lot of
code...

Perhaps I'll just create a project, which copies the new files over the old
ones :)
This should work as well, shouldn't it?



"Mr.Tickle" <MrTickle@mrmen .com> wrote in message
news:ePgQ9TVaDH A.2304@TK2MSFTN GP10.phx.gbl...[color=blue]
>[/color]
http://msdn.microsoft.com/library/de...us/cpref/html/[color=blue]
> frlrfSystemRefl ectionAssemblyC lassLoadTopic.a sp
>
> Use reflection.
>
>
> [C#]
> using System;
> using System.Reflecti on;
>
> class Class1
> {
> public static void Main()
> {
> Assembly SampleAssembly;
> // You must supply a valid fully qualified assembly name here.
> SampleAssembly = Assembly.Load(" Assembly text name, Version,
> Culture, PublicKeyToken" );
> Type[] Types = SampleAssembly. GetTypes();
> // Display all the types contained in the specified assembly.
> foreach (Type oType in Types)
> {
> Console.WriteLi ne(oType.Name.T oString());
> }
> }
> }
>
> "Saso Zagoranski" <saso.zagoransk i@guest.arnes.s i> wrote in message
> news:bi7a6u$sov $1@planja.arnes .si...[color=green]
> > Hi!
> >
> > I have developed an application which I'm about to distribute to my[/color]
> clients.[color=green]
> > It's a pretty big project so bugs are sure to be found somewhere along[/color][/color]
the[color=blue][color=green]
> > line or updates will be needed.
> > What I would like to know is how are patches for applications are made.
> > I wouldn't like to send .dll files to clients and ask them to copy the[/color]
> files[color=green]
> > in their install dir.
> > I've heard about versioning for assemblies, where you just send a new
> > assembly, which
> > has a higher version number? How can you then specify which assembly[/color]
> should[color=green]
> > be used?
> >
> > Thanks,
> > saso
> >
> >
> >[/color]
>
>[/color]

[Rob Tillie]

Re: updating an application

Check out the updater application block at MSDN:

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

This may address your needs.

Greetz,
-- Rob.

Saso Zagoranski wrote:[color=blue]
> That means that instead of referencing the assemblies in VS.net I
> would have to manually load them at runtime?
> How can I then access then access the classes from that assembly...
> assembly.class?
> So "using" can't be used anymore? I would have to change quite a lot
> of code...
>
> Perhaps I'll just create a project, which copies the new files over
> the old ones :)
> This should work as well, shouldn't it?
>
>
>
> "Mr.Tickle" <MrTickle@mrmen .com> wrote in message
> news:ePgQ9TVaDH A.2304@TK2MSFTN GP10.phx.gbl...[color=green]
>>[/color]
>[/color]
http://msdn.microsoft.com/library/de...us/cpref/html/[color=blue][color=green]
>> frlrfSystemRefl ectionAssemblyC lassLoadTopic.a sp
>>
>> Use reflection.
>>
>>
>> [C#]
>> using System;
>> using System.Reflecti on;
>>
>> class Class1
>> {
>> public static void Main()
>> {
>> Assembly SampleAssembly;
>> // You must supply a valid fully qualified assembly name
>> here. SampleAssembly = Assembly.Load(" Assembly text name,
>> Version,
>> Culture, PublicKeyToken" );
>> Type[] Types = SampleAssembly. GetTypes();
>> // Display all the types contained in the specified assembly.
>> foreach (Type oType in Types)
>> {
>> Console.WriteLi ne(oType.Name.T oString());
>> }
>> }
>> }
>>
>> "Saso Zagoranski" <saso.zagoransk i@guest.arnes.s i> wrote in message
>> news:bi7a6u$sov $1@planja.arnes .si...[color=darkred]
>>> Hi!
>>>
>>> I have developed an application which I'm about to distribute to my
>>> clients. It's a pretty big project so bugs are sure to be found
>>> somewhere along the line or updates will be needed.
>>> What I would like to know is how are patches for applications are
>>> made. I wouldn't like to send .dll files to clients and ask them to
>>> copy the files in their install dir.
>>> I've heard about versioning for assemblies, where you just send a
>>> new assembly, which
>>> has a higher version number? How can you then specify which
>>> assembly should be used?
>>>
>>> Thanks,
>>> saso[/color][/color][/color]

[Frank Drebin]

Re: updating an application

Whoa! that was a great article!!

"Rob Tillie" <Rob.Tillie@stu dent.tul.edu> wrote in message
news:OAjvtZWaDH A.2344@TK2MSFTN GP09.phx.gbl...[color=blue]
> Check out the updater application block at MSDN:
>[/color]
http://msdn.microsoft.com/library/de...ml/updater.asp[color=blue]
>
> This may address your needs.
>
> Greetz,
> -- Rob.
>
> Saso Zagoranski wrote:[color=green]
> > That means that instead of referencing the assemblies in VS.net I
> > would have to manually load them at runtime?
> > How can I then access then access the classes from that assembly...
> > assembly.class?
> > So "using" can't be used anymore? I would have to change quite a lot
> > of code...
> >
> > Perhaps I'll just create a project, which copies the new files over
> > the old ones :)
> > This should work as well, shouldn't it?
> >
> >
> >
> > "Mr.Tickle" <MrTickle@mrmen .com> wrote in message
> > news:ePgQ9TVaDH A.2304@TK2MSFTN GP10.phx.gbl...[color=darkred]
> >>[/color]
> >[/color]
>[/color]
http://msdn.microsoft.com/library/de...us/cpref/html/[color=blue][color=green][color=darkred]
> >> frlrfSystemRefl ectionAssemblyC lassLoadTopic.a sp
> >>
> >> Use reflection.
> >>
> >>
> >> [C#]
> >> using System;
> >> using System.Reflecti on;
> >>
> >> class Class1
> >> {
> >> public static void Main()
> >> {
> >> Assembly SampleAssembly;
> >> // You must supply a valid fully qualified assembly name
> >> here. SampleAssembly = Assembly.Load(" Assembly text name,
> >> Version,
> >> Culture, PublicKeyToken" );
> >> Type[] Types = SampleAssembly. GetTypes();
> >> // Display all the types contained in the specified assembly.
> >> foreach (Type oType in Types)
> >> {
> >> Console.WriteLi ne(oType.Name.T oString());
> >> }
> >> }
> >> }
> >>
> >> "Saso Zagoranski" <saso.zagoransk i@guest.arnes.s i> wrote in message
> >> news:bi7a6u$sov $1@planja.arnes .si...
> >>> Hi!
> >>>
> >>> I have developed an application which I'm about to distribute to my
> >>> clients. It's a pretty big project so bugs are sure to be found
> >>> somewhere along the line or updates will be needed.
> >>> What I would like to know is how are patches for applications are
> >>> made. I wouldn't like to send .dll files to clients and ask them to
> >>> copy the files in their install dir.
> >>> I've heard about versioning for assemblies, where you just send a
> >>> new assembly, which
> >>> has a higher version number? How can you then specify which
> >>> assembly should be used?
> >>>
> >>> Thanks,
> >>> saso[/color][/color]
>
>[/color]