Message to plug-in devs...

[Eric Reed]

ATTENTION Plug-in Devs:

 

We will be releasing a maintenance release (I think) sometime today.  I will wait for Sam to be up so he can create an announcement but I think it is ready.  The version will be changing to 2.2.3.  All of your plug-ins should run fine, but you may want to re-build them with a tested version of 2.2.3 so that people don't get warning messages when they install after upgrading.

[Jas Manghera]

Configurator still displays an error message when shutting down.

 

Also I was updating a plugin and the same thing happened, configurator crashed even though the plugin appears to have successfully installed.

 

This is all with the latest trunk code (compiled 2 minutes ago at time of writing).

[Eric Reed]

Configurator has been running fine for me for weeks.   One thing to check - be sure you actually install the new rev of MB via the installer.  Once the version number changes, plugins go completely goofy (won't load) if you only build and do a devinstall.  The actual install package has to be run once with the new version number...

--
You received this message because you are subscribed to the Google Groups "VideoBrowser Devs" group.
To post to this group, send email to videobro...@googlegroups.com.
To unsubscribe from this group, send email to videobrowser-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/videobrowser-devs?hl=en.

[Jas Manghera]

Why is this? what is happening here? I have a feeling I just pushed a new version of Diamond without installing Pegasus that is generating issues for some people but not for others.

 

To clarify, to resolve this matter I should:

 

1) Install Pegasus via google code download.

2) Re-compile Diamond

3) Push Diamond.dll to plugins

 

yes?

[Rob]

Hmmm... maybe Eric slipped something in the configurator so his
CoverArt can overtake Diamond in downloads ;)

In all seriousness, I haven't heard any reports from this happening on
my Themes, I haven't done anything different then the steps you
mentioned. I have also made no changes to the plugin.cs file except
upping the latest version string, I left the RequiredVersion at 2.2.2
and simply changed the TestedVersion to 2.2.3.

Other than that do you know if the problem is specific to Vista or W7
users?

On Mar 12, 8:23 am, Jas Manghera <jmangh...@gmail.com> wrote:
> Why is this? what is happening here? I have a feeling I just pushed a new
> version of Diamond without installing Pegasus that is generating issues for
> some people but not for others.
>
> To clarify, to resolve this matter I should:
>
> 1) Install Pegasus via google code download.
> 2) Re-compile Diamond
> 3) Push Diamond.dll to plugins
>
> yes?
>

> On Wed, Mar 10, 2010 at 8:24 PM, Eric Reed <s...@reedsplace.com> wrote:
> >  Configurator has been running fine for me for weeks.   One thing to check
> > - be sure you actually install the new rev of MB via the installer.  Once
> > the version number changes, plugins go completely goofy (won't load) if you
> > only build and do a devinstall.  The actual install package has to be run
> > once with the new version number...
>

> > *From:* Jas Manghera [mailto:jmangh...@gmail.com]
> > *Sent:* Wednesday, March 10, 2010 2:21 PM
> > *To:* videobro...@googlegroups.com
> > *Subject:* Re: Message to plug-in devs...

>
> > Configurator still displays an error message when shutting down.
>
> > Also I was updating a plugin and the same thing happened, configurator
> > crashed even though the plugin appears to have successfully installed.
>
> > This is all with the latest trunk code (compiled 2 minutes ago at time of
> > writing).
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "VideoBrowser Devs" group.
> > To post to this group, send email to videobro...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > videobrowser-d...@googlegroups.com<videobrowser-devs%2Bunsu...@googlegroups.com>

> > .
> > For more options, visit this group at
> >http://groups.google.com/group/videobrowser-devs?hl=en.
>
> >   --
> > You received this message because you are subscribed to the Google Groups
> > "VideoBrowser Devs" group.
> > To post to this group, send email to videobro...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > videobrowser-d...@googlegroups.com<videobrowser-devs%2Bunsu...@googlegroups.com>

[Eric Reed]

You should only have to do step one to get it to work.  Where I have run into issues is when the version number changes, if I just build mediabrowser and let it do a devinstall from the IDE then none of the current plug-ins will load.  If I just run the msi once (with the new version) then all the plug-ins work fine - without touching them.

 

My guess is that the install routine adjusts some registry settings that the devinstall doesn't.

[Jas Manghera]

This is what I did:

 

1) I installed pegasus through a compilation of Media Browser source code not any installer.

2) Recompiled plugin

3) Released.

 

So just to be absolutely crystal clear, I should have done step 1 differently and installed pegasus through an installer build?

 

 

 

To unsubscribe from this group, send email to videobrowser-d...@googlegroups.com.

[Eric Reed]

Maybe - but only to get it to load properly on your machine.   I think your plug-in should be fine for anyone who installed via the msi.  I don't think re-compiling it against the new version (just because of a version number change) is necessary.  That is to say, any issues you are having, I don't think are related to this...

[Sam Saffron]

Yeah, you should make sure you are referencing mediabrowser 2.2.3 in your plugin project, there were some changed interfaces though I doubt you were affected by them 

[Jas Manghera]

I ended up re-referencing everything. My early guess is either my MB reference got broken or something went wrong with a vista .dll reference.