|
|
You're in the
dotnet remoting
group:Windows service and remoting
dotnet remoting:
and a Web application.I need to add a windows service to this solution and add the business logic layer as a reference to my windows service.We are in development phase and it's very probable that the business layer is changed.They promise to keep the interface intact.I mean they promise to keep the name of the method I need always "Upload" ,but they might change the assembly and compile it into the new version. I was thinking if there is a technique like Reflection,Remoting or latebinding or whatever it is which I can use and get rid of compiling my windows service whenever they change the business layer and complie it to a newer version.I was reading this article http://www.15seconds.com/issue/021015.htm and I just wondered if I could business logic layer as a plug in into my windows service. Any suggestions? Thanks P.S windows service and web application might be in different boxes.
Ray,
You can actually solve this pretty easily with an assembly binding redirect. Here's the msdn info: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconAssemblyVersionRedirection.asp Since what you want is really to redirect to an OLDER version (the version that is sitting with the windows service) it would look something like this: <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="TheServerAssembly" publicKeyToken="86d3cc6071f2ab51" culture="neutral" /> <!-- This says that for this range of versions on the server, always use the build I have on the client. --> <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="1.0.5.22885"/> </dependentAssembly> </assemblyBinding> </runtime> Put this section after this tag: </system.runtime.remoting> and before the last tag in your App.config: </configuration> Just replace name, publicKeyToken and newVersion with your appropriate values and you should be good to go as long as they do not change the public interfaces and types. HTH, -B [quoted text, click to view] "Ray5531" <RayAll@microsft.com> wrote in message news:O6s5CuCUFHA.2768@tk2msftngp13.phx.gbl... > We have a solution consists of an O/R mapper project,Business Logice layer > and a Web application.I need to add a windows service to this solution and > add the business logic layer as a reference to my windows service.We are > in development phase and it's very probable that the business layer is > changed.They promise to keep the interface intact.I mean they promise to > keep the name of the method I need always "Upload" ,but they might change > the assembly and compile it into the new version. > > I was thinking if there is a technique like Reflection,Remoting or > latebinding or whatever it is which I can use and get rid of compiling my > windows service whenever they change the business layer and complie it to > a newer version.I was reading this article > http://www.15seconds.com/issue/021015.htm and I just wondered if I could > business logic layer as a plug in into my windows service. > > Any suggestions? > > Thanks > > P.S windows service and web application might be in different boxes. >
Thanks Beth ,
I think it's much better than using remoting ,because in that approach I have to ask them to make their object inherit from MarshalByRef and change their configuration file,but in this way I will change my app. Right?? Thanks for your help [quoted text, click to view] "Beth Massi [Architect MVP]" <bmassi@comcast.net> wrote in message news:u1CotYeUFHA.3076@TK2MSFTNGP12.phx.gbl... > Ray, > > You can actually solve this pretty easily with an assembly binding > redirect. Here's the msdn info: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconAssemblyVersionRedirection.asp > > Since what you want is really to redirect to an OLDER version (the version > that is sitting with the windows service) it would look something like > this: > > <runtime> > <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> > <dependentAssembly> > <assemblyIdentity name="TheServerAssembly" > publicKeyToken="86d3cc6071f2ab51" > culture="neutral" > /> > <!-- This says that for this range of versions on the server, > always use the build I have on the client. --> > <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" > newVersion="1.0.5.22885"/> > </dependentAssembly> > </assemblyBinding> > </runtime> > > Put this section after this tag: > > </system.runtime.remoting> > > and before the last tag in your App.config: > > </configuration> > > Just replace name, publicKeyToken and newVersion with your appropriate > values and you should be good to go as long as they do not change the > public interfaces and types. > > HTH, > -B > > "Ray5531" <RayAll@microsft.com> wrote in message > news:O6s5CuCUFHA.2768@tk2msftngp13.phx.gbl... >> We have a solution consists of an O/R mapper project,Business Logice >> layer and a Web application.I need to add a windows service to this >> solution and add the business logic layer as a reference to my windows >> service.We are in development phase and it's very probable that the >> business layer is changed.They promise to keep the interface intact.I >> mean they promise to keep the name of the method I need always "Upload" >> ,but they might change the assembly and compile it into the new version. >> >> I was thinking if there is a technique like Reflection,Remoting or >> latebinding or whatever it is which I can use and get rid of compiling my >> windows service whenever they change the business layer and complie it to >> a newer version.I was reading this article >> http://www.15seconds.com/issue/021015.htm and I just wondered if I could >> business logic layer as a plug in into my windows service. >> >> Any suggestions? >> >> Thanks >> >> P.S windows service and web application might be in different boxes. >> > >
Yes you change your App.config file, BUT you still will be using remoting.
You're just telling your application to use the TYPES (metadata) from the assembly located with your client, but at runtime you will still be communicating with the remote components. This will work as long as the public types match in both the server assembly and your client assembly. So this means that the server component is free to change the implementation (but NOT the interface), and you will be running the updated implementation at runtime. [quoted text, click to view] "Ray5531" <Ray5531@microsoft.com> wrote in message news:esfr$6gUFHA.3056@TK2MSFTNGP14.phx.gbl... > Thanks Beth , > I think it's much better than using remoting ,because in that approach I > have to ask them to make their object inherit from MarshalByRef and change > their configuration file,but in this way I will change my app. > Right?? > > Thanks for your help > > "Beth Massi [Architect MVP]" <bmassi@comcast.net> wrote in message > news:u1CotYeUFHA.3076@TK2MSFTNGP12.phx.gbl... >> Ray, >> >> You can actually solve this pretty easily with an assembly binding >> redirect. Here's the msdn info: >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconAssemblyVersionRedirection.asp >> >> Since what you want is really to redirect to an OLDER version (the >> version that is sitting with the windows service) it would look something >> like this: >> >> <runtime> >> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> >> <dependentAssembly> >> <assemblyIdentity name="TheServerAssembly" >> publicKeyToken="86d3cc6071f2ab51" >> culture="neutral" >> /> >> <!-- This says that for this range of versions on the server, >> always use the build I have on the client. --> >> <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" >> newVersion="1.0.5.22885"/> >> </dependentAssembly> >> </assemblyBinding> >> </runtime> >> >> Put this section after this tag: >> >> </system.runtime.remoting> >> >> and before the last tag in your App.config: >> >> </configuration> >> >> Just replace name, publicKeyToken and newVersion with your appropriate >> values and you should be good to go as long as they do not change the >> public interfaces and types. >> >> HTH, >> -B >> >> "Ray5531" <RayAll@microsft.com> wrote in message >> news:O6s5CuCUFHA.2768@tk2msftngp13.phx.gbl... >>> We have a solution consists of an O/R mapper project,Business Logice >>> layer and a Web application.I need to add a windows service to this >>> solution and add the business logic layer as a reference to my windows >>> service.We are in development phase and it's very probable that the >>> business layer is changed.They promise to keep the interface intact.I >>> mean they promise to keep the name of the method I need always "Upload" >>> ,but they might change the assembly and compile it into the new version. >>> >>> I was thinking if there is a technique like Reflection,Remoting or >>> latebinding or whatever it is which I can use and get rid of compiling >>> my windows service whenever they change the business layer and complie >>> it to a newer version.I was reading this article >>> http://www.15seconds.com/issue/021015.htm and I just wondered if I could >>> business logic layer as a plug in into my windows service. >>> >>> Any suggestions? >>> >>> Thanks >>> >>> P.S windows service and web application might be in different boxes. >>> >> >> > >
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 |