| Groups | Blog | Home |
dotnet remoting : Is remoting what I'm thinking about?
I have several different dll's that I use in my asp.net development. One of
them is used for sending email, another creates a dropdown menu with various service codes, there are others too. The plus side to these classes is that it provides consistant info, and it also allows me save time by reusuing code. Now for my question. Say, for instance, the name of our mail server changes. Unless I update the code for the mail class I created, the emails that my asp.net pages send will fail. Not a problem, all I have to do is update the mailserver in the code, and recompile it. The problem is that I'd have to also recompile all the apps that use that class. I'd like to have 1 copy of the dll on the server, and have all my apps refer to that dll. That way, I can just drop my new dll in the folder, and be done with it. I know what I'm
Normally you would find that information in configuration files for the
applications rather than in a compiled DLL. Remoting is likely not what you are looking for. Fred [quoted text, click to view] "Casey" <Casey@discussions.microsoft.com> wrote in message news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > I have several different dll's that I use in my asp.net development. One of > them is used for sending email, another creates a dropdown menu with various > service codes, there are others too. The plus side to these classes is that > it provides consistant info, and it also allows me save time by reusuing code. > > Now for my question. Say, for instance, the name of our mail server changes. > Unless I update the code for the mail class I created, the emails that my > asp.net pages send will fail. Not a problem, all I have to do is update the > mailserver in the code, and recompile it. The problem is that I'd have to > also recompile all the apps that use that class. I'd like to have 1 copy of > the dll on the server, and have all my apps refer to that dll. That way, I > can just drop my new dll in the folder, and be done with it. I know what I'm > trying to do can be done, I just don't know how...
This isn't remoting related -- what you need to do is place your assembly in
the GAC. This is where you put shared assemblies so you can update them in a single place. Ken [quoted text, click to view] "Casey" <Casey@discussions.microsoft.com> wrote in message news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > I have several different dll's that I use in my asp.net development. One of > them is used for sending email, another creates a dropdown menu with various > service codes, there are others too. The plus side to these classes is that > it provides consistant info, and it also allows me save time by reusuing code. > > Now for my question. Say, for instance, the name of our mail server changes. > Unless I update the code for the mail class I created, the emails that my > asp.net pages send will fail. Not a problem, all I have to do is update the > mailserver in the code, and recompile it. The problem is that I'd have to > also recompile all the apps that use that class. I'd like to have 1 copy of > the dll on the server, and have all my apps refer to that dll. That way, I > can just drop my new dll in the folder, and be done with it. I know what I'm > trying to do can be done, I just don't know how...
Any suggestions for what to use then?
[quoted text, click to view] "Fred Hirschfeld" wrote:
> Normally you would find that information in configuration files for the > applications rather than in a compiled DLL. Remoting is likely not what you > are looking for. > > Fred > > "Casey" <Casey@discussions.microsoft.com> wrote in message > news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > > I have several different dll's that I use in my asp.net development. One > of > > them is used for sending email, another creates a dropdown menu with > various > > service codes, there are others too. The plus side to these classes is > that > > it provides consistant info, and it also allows me save time by reusuing > code. > > > > Now for my question. Say, for instance, the name of our mail server > changes. > > Unless I update the code for the mail class I created, the emails that my > > asp.net pages send will fail. Not a problem, all I have to do is update > the > > mailserver in the code, and recompile it. The problem is that I'd have to > > also recompile all the apps that use that class. I'd like to have 1 copy > of > > the dll on the server, and have all my apps refer to that dll. That way, I > > can just drop my new dll in the folder, and be done with it. I know what > I'm > > trying to do can be done, I just don't know how... > >
Score! Thats exactly what I'm looking to do. Thanks.
[quoted text, click to view] "Ken Kolda" wrote:
> This isn't remoting related -- what you need to do is place your assembly in > the GAC. This is where you put shared assemblies so you can update them in a > single place. > > Ken > > > "Casey" <Casey@discussions.microsoft.com> wrote in message > news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > > I have several different dll's that I use in my asp.net development. One > of > > them is used for sending email, another creates a dropdown menu with > various > > service codes, there are others too. The plus side to these classes is > that > > it provides consistant info, and it also allows me save time by reusuing > code. > > > > Now for my question. Say, for instance, the name of our mail server > changes. > > Unless I update the code for the mail class I created, the emails that my > > asp.net pages send will fail. Not a problem, all I have to do is update > the > > mailserver in the code, and recompile it. The problem is that I'd have to > > also recompile all the apps that use that class. I'd like to have 1 copy > of > > the dll on the server, and have all my apps refer to that dll. That way, I > > can just drop my new dll in the folder, and be done with it. I know what > I'm > > trying to do can be done, I just don't know how... > >
Thats also a very good point. Thanks for the advice.
[quoted text, click to view] "Dumitru Sbenghe" wrote:
> I guess Fred want to say, what I think also, that it is unreasonable to > compile a mail send dll only because the mail server name has changed. > > Make the dll used to send email (the classes inside it) to accept the name > of the mail server as parameter. And the mail server can be configured > externally in the application config file or a similar place; it depends of > your requirements and restrictions. > > Dumitru Sbenghe > > "Casey" <Casey@discussions.microsoft.com> wrote in message > news:3E7DE807-BB21-4FB9-B277-2889027049BA@microsoft.com... > > Any suggestions for what to use then? > > > > "Fred Hirschfeld" wrote: > > > > > Normally you would find that information in configuration files for the > > > applications rather than in a compiled DLL. Remoting is likely not what > you > > > are looking for. > > > > > > Fred > > > > > > "Casey" <Casey@discussions.microsoft.com> wrote in message > > > news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > > > > I have several different dll's that I use in my asp.net development. > One > > > of > > > > them is used for sending email, another creates a dropdown menu with > > > various > > > > service codes, there are others too. The plus side to these classes is > > > that > > > > it provides consistant info, and it also allows me save time by > reusuing > > > code. > > > > > > > > Now for my question. Say, for instance, the name of our mail server > > > changes. > > > > Unless I update the code for the mail class I created, the emails that > my > > > > asp.net pages send will fail. Not a problem, all I have to do is > update > > > the > > > > mailserver in the code, and recompile it. The problem is that I'd have > to > > > > also recompile all the apps that use that class. I'd like to have 1 > copy > > > of > > > > the dll on the server, and have all my apps refer to that dll. That > way, I > > > > can just drop my new dll in the folder, and be done with it. I know > what > > > I'm > > > > trying to do can be done, I just don't know how... > > > > > > > > > > >
I guess Fred want to say, what I think also, that it is unreasonable to
compile a mail send dll only because the mail server name has changed. Make the dll used to send email (the classes inside it) to accept the name of the mail server as parameter. And the mail server can be configured externally in the application config file or a similar place; it depends of your requirements and restrictions. Dumitru Sbenghe [quoted text, click to view] "Casey" <Casey@discussions.microsoft.com> wrote in message news:3E7DE807-BB21-4FB9-B277-2889027049BA@microsoft.com... > Any suggestions for what to use then? > > "Fred Hirschfeld" wrote: > > > Normally you would find that information in configuration files for the > > applications rather than in a compiled DLL. Remoting is likely not what you > > are looking for. > > > > Fred > > > > "Casey" <Casey@discussions.microsoft.com> wrote in message > > news:3B11BFC3-D81C-4B54-A9C0-E0652F99EEF9@microsoft.com... > > > I have several different dll's that I use in my asp.net development. One > > of > > > them is used for sending email, another creates a dropdown menu with > > various > > > service codes, there are others too. The plus side to these classes is > > that > > > it provides consistant info, and it also allows me save time by reusuing > > code. > > > > > > Now for my question. Say, for instance, the name of our mail server > > changes. > > > Unless I update the code for the mail class I created, the emails that my > > > asp.net pages send will fail. Not a problem, all I have to do is update > > the > > > mailserver in the code, and recompile it. The problem is that I'd have to > > > also recompile all the apps that use that class. I'd like to have 1 copy > > of > > > the dll on the server, and have all my apps refer to that dll. That way, I > > > can just drop my new dll in the folder, and be done with it. I know what > > I'm > > > trying to do can be done, I just don't know how... > > > > > >
Hi Casey,
how about using a configuration file to store the mail server name and refer the same from your class. No need to recompile any dll's in such a scenario. HTH. Kaustav. [quoted text, click to view] "Casey" wrote:
> I have several different dll's that I use in my asp.net development. One of > them is used for sending email, another creates a dropdown menu with various > service codes, there are others too. The plus side to these classes is that > it provides consistant info, and it also allows me save time by reusuing code. > > Now for my question. Say, for instance, the name of our mail server changes. > Unless I update the code for the mail class I created, the emails that my > asp.net pages send will fail. Not a problem, all I have to do is update the > mailserver in the code, and recompile it. The problem is that I'd have to > also recompile all the apps that use that class. I'd like to have 1 copy of > the dll on the server, and have all my apps refer to that dll. That way, I > can just drop my new dll in the folder, and be done with it. I know what I'm
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |