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" <Mr******@mrmen.com> wrote in message
news:eP**************@TK2MSFTNGP10.phx.gbl...
http://msdn.microsoft.com/library/de...us/cpref/html/ frlrfSystemReflectionAssemblyClassLoadTopic.asp
Use reflection.
[C#]
using System;
using System.Reflection;
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.WriteLine(oType.Name.ToString());
}
}
}
"Saso Zagoranski" <sa*************@guest.arnes.si> wrote in message
news:bi**********@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