Vista - Loading ?

09-01-2008

I'm currently writing some plug-in modules for a system that somebody else
is developing. They have provided my with an interface to implement, and
when I do, everything loads into their system fine.

I basically just implement their interface, and add a reference to their
library in VS2008.

However, a problem arises when they update their library version. My
plug-in will no longer load into their system.

Their directory structure looks like the following:

\Root dir with library version C\
\Root dir with library version C\subdirectory with plugin referencing
library version B\
\Root dir with library version C\subdirectory with plugin referencing
library version A\

Each subdirectory underneath the root has the version of the library located
in that directory. However, I think their system is loading version C, and
then not loading the appropriate plugins because those plugins were build
referencing a difference version of library.

They do not want to put every version of the library in the GAC. Is there
an easy way to fix this versioning problem so that all of the plugins will
load correctly?

Thanks.

09-02-2008

"Tom" <johnthompson1@xxxxxx> wrote in message
news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx

Quote:

> I'm currently writing some plug-in modules for a system that somebody else
> is developing. They have provided my with an interface to implement, and
> when I do, everything loads into their system fine.
>
> I basically just implement their interface, and add a reference to their
> library in VS2008.
>
> However, a problem arises when they update their library version. My
> plug-in will no longer load into their system.
>
> Their directory structure looks like the following:
>
> \Root dir with library version C\
> \Root dir with library version C\subdirectory with plugin referencing
> library version B\
> \Root dir with library version C\subdirectory with plugin referencing
> library version A\
>
> Each subdirectory underneath the root has the version of the library
> located in that directory. However, I think their system is loading
> version C, and then not loading the appropriate plugins because those
> plugins were build referencing a difference version of library.
>
> They do not want to put every version of the library in the GAC. Is there
> an easy way to fix this versioning problem so that all of the plugins will
> load correctly?

If the newer version of their library didn't change the interface (or
otherwise broke compatibility), then you could just avoid referencing the
specific version of their assembly (Specific Version = False in Properties
window for the reference).

09-02-2008

"Pavel Minaev" <int19h@xxxxxx> wrote in message
news:%23AmM$5LDJHA.5316@xxxxxx

Quote:

> "Tom" <johnthompson1@xxxxxx> wrote in message
> news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx

Quote:

>> I'm currently writing some plug-in modules for a system that somebody
>> else is developing. They have provided my with an interface to
>> implement, and when I do, everything loads into their system fine.
>>
>> I basically just implement their interface, and add a reference to their
>> library in VS2008.
>>
>> However, a problem arises when they update their library version. My
>> plug-in will no longer load into their system.
>>
>> Their directory structure looks like the following:
>>
>> \Root dir with library version C\
>> \Root dir with library version C\subdirectory with plugin referencing
>> library version B\
>> \Root dir with library version C\subdirectory with plugin referencing
>> library version A\
>>
>> Each subdirectory underneath the root has the version of the library
>> located in that directory. However, I think their system is loading
>> version C, and then not loading the appropriate plugins because those
>> plugins were build referencing a difference version of library.
>>
>> They do not want to put every version of the library in the GAC. Is
>> there an easy way to fix this versioning problem so that all of the
>> plugins will load correctly?

>
> If the newer version of their library didn't change the interface (or
> otherwise broke compatibility), then you could just avoid referencing the
> specific version of their assembly (Specific Version = False in Properties
> window for the reference).
>
>

Thanks Pavel,

It looks as though VS2008 set that setting as false by default. I'll go
back and make sure that their interface did not change.

Thanks again.
-- Tom

09-05-2008

"Tom" <johnthompson1@xxxxxx> wrote in message
news:CECCC580-8E72-4898-BF5E-9663C711421F@xxxxxx

Quote:

>
> "Pavel Minaev" <int19h@xxxxxx> wrote in message
> news:%23AmM$5LDJHA.5316@xxxxxx

Quote:

>> "Tom" <johnthompson1@xxxxxx> wrote in message
>> news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx

Quote:

>>> I'm currently writing some plug-in modules for a system that somebody
>>> else is developing. They have provided my with an interface to
>>> implement, and when I do, everything loads into their system fine.
>>>
>>> I basically just implement their interface, and add a reference to their
>>> library in VS2008.
>>>
>>> However, a problem arises when they update their library version. My
>>> plug-in will no longer load into their system.
>>>
>>> Their directory structure looks like the following:
>>>
>>> \Root dir with library version C\
>>> \Root dir with library version C\subdirectory with plugin referencing
>>> library version B\
>>> \Root dir with library version C\subdirectory with plugin referencing
>>> library version A\
>>>
>>> Each subdirectory underneath the root has the version of the library
>>> located in that directory. However, I think their system is loading
>>> version C, and then not loading the appropriate plugins because those
>>> plugins were build referencing a difference version of library.
>>>
>>> They do not want to put every version of the library in the GAC. Is
>>> there an easy way to fix this versioning problem so that all of the
>>> plugins will load correctly?

>>
>> If the newer version of their library didn't change the interface (or
>> otherwise broke compatibility), then you could just avoid referencing the
>> specific version of their assembly (Specific Version = False in
>> Properties window for the reference).
>>
>>

>
> Thanks Pavel,
>
> It looks as though VS2008 set that setting as false by default. I'll go
> back and make sure that their interface did not change.
>
> Thanks again.
> -- Tom
>

Well, according to them, their interface hasn't changed in quite a while.
Any other ideas?

Thanks again.

09-06-2008

"Tom" <johnthompson1@xxxxxx> wrote in message
news:0A5F6D67-7E51-429C-9483-41893BDF162D@xxxxxx

Quote:

> Well, according to them, their interface hasn't changed in quite a while.
> Any other ideas?

Can you obtain and post the code that describes how they programmatically
load those plugins?

09-01-2008	#1 (permalink)
Tom n/a posts	Loading ? I'm currently writing some plug-in modules for a system that somebody else is developing. They have provided my with an interface to implement, and when I do, everything loads into their system fine. I basically just implement their interface, and add a reference to their library in VS2008. However, a problem arises when they update their library version. My plug-in will no longer load into their system. Their directory structure looks like the following: \Root dir with library version C\ \Root dir with library version C\subdirectory with plugin referencing library version B\ \Root dir with library version C\subdirectory with plugin referencing library version A\ Each subdirectory underneath the root has the version of the library located in that directory. However, I think their system is loading version C, and then not loading the appropriate plugins because those plugins were build referencing a difference version of library. They do not want to put every version of the library in the GAC. Is there an easy way to fix this versioning problem so that all of the plugins will load correctly? Thanks.
My System Specs

09-02-2008	#2 (permalink)
Pavel Minaev n/a posts	Re: Loading ? "Tom" <johnthompson1@xxxxxx> wrote in message news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx Quote: > I'm currently writing some plug-in modules for a system that somebody else > is developing. They have provided my with an interface to implement, and > when I do, everything loads into their system fine. > > I basically just implement their interface, and add a reference to their > library in VS2008. > > However, a problem arises when they update their library version. My > plug-in will no longer load into their system. > > Their directory structure looks like the following: > > \Root dir with library version C\ > \Root dir with library version C\subdirectory with plugin referencing > library version B\ > \Root dir with library version C\subdirectory with plugin referencing > library version A\ > > Each subdirectory underneath the root has the version of the library > located in that directory. However, I think their system is loading > version C, and then not loading the appropriate plugins because those > plugins were build referencing a difference version of library. > > They do not want to put every version of the library in the GAC. Is there > an easy way to fix this versioning problem so that all of the plugins will > load correctly? If the newer version of their library didn't change the interface (or otherwise broke compatibility), then you could just avoid referencing the specific version of their assembly (Specific Version = False in Properties window for the reference).
My System Specs

09-02-2008	#3 (permalink)
Tom n/a posts	Re: Loading ? "Pavel Minaev" <int19h@xxxxxx> wrote in message news:%23AmM$5LDJHA.5316@xxxxxx Quote: > "Tom" <johnthompson1@xxxxxx> wrote in message > news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx Quote: >> I'm currently writing some plug-in modules for a system that somebody >> else is developing. They have provided my with an interface to >> implement, and when I do, everything loads into their system fine. >> >> I basically just implement their interface, and add a reference to their >> library in VS2008. >> >> However, a problem arises when they update their library version. My >> plug-in will no longer load into their system. >> >> Their directory structure looks like the following: >> >> \Root dir with library version C\ >> \Root dir with library version C\subdirectory with plugin referencing >> library version B\ >> \Root dir with library version C\subdirectory with plugin referencing >> library version A\ >> >> Each subdirectory underneath the root has the version of the library >> located in that directory. However, I think their system is loading >> version C, and then not loading the appropriate plugins because those >> plugins were build referencing a difference version of library. >> >> They do not want to put every version of the library in the GAC. Is >> there an easy way to fix this versioning problem so that all of the >> plugins will load correctly? > > If the newer version of their library didn't change the interface (or > otherwise broke compatibility), then you could just avoid referencing the > specific version of their assembly (Specific Version = False in Properties > window for the reference). > > Thanks Pavel, It looks as though VS2008 set that setting as false by default. I'll go back and make sure that their interface did not change. Thanks again. -- Tom
My System Specs

09-05-2008	#4 (permalink)
Tom n/a posts	Re: Loading ? "Tom" <johnthompson1@xxxxxx> wrote in message news:CECCC580-8E72-4898-BF5E-9663C711421F@xxxxxx Quote: > > "Pavel Minaev" <int19h@xxxxxx> wrote in message > news:%23AmM$5LDJHA.5316@xxxxxx Quote: >> "Tom" <johnthompson1@xxxxxx> wrote in message >> news:B5744CCC-5606-477D-A45C-E581E79C2023@xxxxxx Quote: >>> I'm currently writing some plug-in modules for a system that somebody >>> else is developing. They have provided my with an interface to >>> implement, and when I do, everything loads into their system fine. >>> >>> I basically just implement their interface, and add a reference to their >>> library in VS2008. >>> >>> However, a problem arises when they update their library version. My >>> plug-in will no longer load into their system. >>> >>> Their directory structure looks like the following: >>> >>> \Root dir with library version C\ >>> \Root dir with library version C\subdirectory with plugin referencing >>> library version B\ >>> \Root dir with library version C\subdirectory with plugin referencing >>> library version A\ >>> >>> Each subdirectory underneath the root has the version of the library >>> located in that directory. However, I think their system is loading >>> version C, and then not loading the appropriate plugins because those >>> plugins were build referencing a difference version of library. >>> >>> They do not want to put every version of the library in the GAC. Is >>> there an easy way to fix this versioning problem so that all of the >>> plugins will load correctly? >> >> If the newer version of their library didn't change the interface (or >> otherwise broke compatibility), then you could just avoid referencing the >> specific version of their assembly (Specific Version = False in >> Properties window for the reference). >> >> > > Thanks Pavel, > > It looks as though VS2008 set that setting as false by default. I'll go > back and make sure that their interface did not change. > > Thanks again. > -- Tom > Well, according to them, their interface hasn't changed in quite a while. Any other ideas? Thanks again.
My System Specs

09-06-2008	#5 (permalink)
Pavel Minaev n/a posts	Re: Loading ? "Tom" <johnthompson1@xxxxxx> wrote in message news:0A5F6D67-7E51-429C-9483-41893BDF162D@xxxxxx Quote: > Well, according to them, their interface hasn't changed in quite a while. > Any other ideas? Can you obtain and post the code that describes how they programmatically load those plugins?
My System Specs

Similar Threads
Thread	Forum
blue screen, vista not loading, error says stopped loading to prot	Vista performance & maintenance
Startup Drivers loading - not loading?	Vista General
loading	Vista General
Loading WMP	Vista music pictures video