(original thread)Extension installer - new way to install extensions (1 Viewer)

Status
Not open for further replies.

dukus

Portal Pro
January 20, 2006
783
748
44
Home Country
Romania Romania
I make some progress...
News:
- Customize the setup (in single setup file, you may include more version of a single file, like SVN and stable version of same plugin )
- Post setup action (when the setup done, run the configuration.exe or a plugin setup)

In dukus.extra.hu the upload option is available, just registration needed.

Thx, goes to Fr team, zebons, Scubefr.

:D
 

zebons

Portal Pro
January 2, 2006
1,484
114
I make some progress...
News:
- Customize the setup (in single setup file, you may include more version of a single file, like SVN and stable version of same plugin )
I see that finally you develop that functionnality ;-))
Nice, how does it work ? Is it based on groups and files mapping into groups ? Where can we declare which file put on each version ?
 

dukus

Portal Pro
January 20, 2006
783
748
44
Home Country
Romania Romania
In Setup->Setup Groups
In first tab define the groups and in second tab map the files to group.
Multiple files with same name isn't allowed, use OuputFileName properties
 

zebons

Portal Pro
January 2, 2006
1,484
114
In Setup->Setup Groups
In first tab define the groups and in second tab map the files to group.
Multiple files with same name isn't allowed, use OuputFileName properties

And Where du you define which group for which version ?
For file renaming it should be better to have an InputFileName Properties, so the file name change only in the package and remain the same for users no need to rename files before importing into the package.
For example : after having imported a dll for a particular version, if you try to import the same filename for another version, MPInstaler ask to define groups first and assign the fisrt dll to one group, the internal filename become <filename>_<group> and the OutFileName is automaticly define with filename value. Now we can import the second dll without any problem and affect it to a second group. So no need to really change the real name. What do you think about ?
 

dukus

Portal Pro
January 20, 2006
783
748
44
Home Country
Romania Romania
The group option was made to help making more packages in single an reuse some files to save some space and bandwidth. Distributing more version the same plugin it is a usage this option, but not necessary the only one. To support more files with same name it is difficulty, needed a lot of code changes and testing and i think usability is low it is hard to identify the files. The support site is now online it is usable and in sort time we migrate to official site, in mean time use my site.

Unlucky nobody want to use this format, and i don't know the reason. :confused:
 

moiristo

Portal Pro
November 17, 2006
342
27
Enschede
Home Country
Netherlands Netherlands
Great that you can now add two versions in one package. I've used it for the UitzendingGemist plugin and found that it works nice, apart from two things:

1) It crashed when I tested it within MP 0.2.2 stable dir. I'm afraid you have to release two versions too :)
2) Is it possible to have 'common files'? For example, in my plugin I use some images that are common for every skin, but it seems I have to add them for every skin I import.
 

luckyme

New Member
June 9, 2007
1
0
Home Country
Netherlands Netherlands
When i start MPI installer it starts up great, but when I select any button it gives me the following error. Any idea how to fix this?

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeLoadException: Could not load type 'MediaPortal.Configuration.Config' from assembly 'Utils, Version=1.0.2546.32604, Culture=neutral, PublicKeyToken=null'.
at MPInstaler.MPInstallHelper..ctor()
at MPInstaler.controlp..ctor()
at MPInstaler.start_form.button3_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MPInstaler
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/Team%20MediaPortal/MediaPortal/MPInstaler.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Utils
Assembly Version: 1.0.2546.32604
Win32 Version: 1.0.2546.32604
CodeBase: file:///C:/Program%20Files/Team%20MediaPortal/MediaPortal/Utils.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 

zebons

Portal Pro
January 2, 2006
1,484
114
When i start MPI installer it starts up great, but when I select any button it gives me the following error. Any idea how to fix this?
Try that version, it's for MP stable 0.2.2 version...
 

dacore944

Portal Member
June 12, 2007
19
1
41
I have installed latest Media Portal v0.2.2.0 and i download the latest version of MediaInstaller date 8-6-2007 15:33 installed in the media portal directory.
I can start the program but when i click a button i the following error.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.TypeLoadException: Could not load type 'MediaPortal.Configuration.Config' from assembly 'Utils, Version=1.0.2546.32604, Culture=neutral, PublicKeyToken=null'.
at MPInstaler.MPInstallHelper..ctor()
at MPInstaler.controlp..ctor()
at MPInstaler.start_form.button3_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MPInstaler
Assembly Version: 1.0.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/Program%20Files/Team%20MediaPortal/MediaPortal/MPInstaller.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Utils
Assembly Version: 1.0.2546.32604
Win32 Version: 1.0.2546.32604
CodeBase: file:///C:/Program%20Files/Team%20MediaPortal/MediaPortal/Utils.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Status
Not open for further replies.

Users who are viewing this thread

Top Bottom