DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Thu, 16 Aug 2007 13:30:32 GMT,    posted on: microsoft.public.dotnet.framework.aspnet        back       

Thread Index
  1    Dica
          2    Mark Rae [MVP]
          3    Dica
                 4    Mark Rae [MVP]
                        5    Dica
          6    Mark Rae [MVP]
          7    DeveloperX
          8    Dica
                 9    Lalit Dubey


best way to do a concurrent installation   
i've got an app that needs to install a named instance of SQL Express. VS 
2005 allows me to specify required components for my setup project, but 
named instances of SQL Express isn't supported. so, my main setup MSI needs 
to execute the SQL Express MSI (a concurrent installation). technically, 
this is possible, but this is frowned upon by MS for various reasons.  so, 
how do i go about pulling this off? i'd be okay if my first setup MSI exits, 
but then i need something to call the SQL Express MSI. as far as i can see, 
there's nothing like an "onExit" event i can use from my setup MSI to call 
and execute the SQL MSI.

what's the best way to pull this off? does installShield offer better 
solutions for situations like this?

tks for any advice.
Date:Thu, 16 Aug 2007 13:30:32 GMT   Author:  

Re: best way to do a concurrent installation   
"Dica"  wrote in message 
news:YjYwi.80127$Io4.41618@edtnps89...


> there's nothing like an "onExit" event i can use from my setup MSI to call 
> and execute the SQL MSI.


Go into Custom Actions, Commit and add a pointer to the SQL Server Express 
MSI - custom actions in this section run at the end of the main installation 
routine...


-- 
Mark Rae
ASP.NET MVP
http://www.markrae.net
Date:Thu, 16 Aug 2007 14:58:59 +0100   Author:  

Re: best way to do a concurrent installation   
"Mark Rae [MVP]"  wrote in message 
news:%23aMJP2A4HHA.2312@TK2MSFTNGP06.phx.gbl...

> "Dica"  wrote in message 
> news:YjYwi.80127$Io4.41618@edtnps89...
>
>> there's nothing like an "onExit" event i can use from my setup MSI to 
>> call and execute the SQL MSI.
>
> Go into Custom Actions, Commit and add a pointer to the SQL Server Express 
> MSI - custom actions in this section run at the end of the main 
> installation routine...
>


i tried that, but it doesn't work. my main setup MSI is calls the SQL MSI 
from the commit action, but the SQL MSI gives me an error message about 
"Another installation is already in progress". any other ideas?


>
> -- 
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net 
Date:Thu, 16 Aug 2007 16:29:57 GMT   Author:  

Re: best way to do a concurrent installation   
"Dica"  wrote in message 
news:9Y_wi.98052$tB5.56079@edtnps90...


>> Go into Custom Actions, Commit and add a pointer to the SQL Server 
>> Express MSI - custom actions in this section run at the end of the main 
>> installation routine...
>>
>
> i tried that, but it doesn't work. my main setup MSI is calls the SQL MSI 
> from the commit action, but the SQL MSI gives me an error message about 
> "Another installation is already in progress". any other ideas?


Hmm - apologies, but I think you may be out of luck, as discussed here: 
http://community.installshield.com/archive/index.php?t-155357.html


-- 
Mark Rae
ASP.NET MVP
http://www.markrae.net
Date:Thu, 16 Aug 2007 17:46:17 +0100   Author:  

Re: best way to do a concurrent installation   
"Mark Rae [MVP]"  wrote in message 
news:e53buTC4HHA.1484@TK2MSFTNGP06.phx.gbl...

> "Dica"  wrote in message 
> news:9Y_wi.98052$tB5.56079@edtnps90...
>
>>> Go into Custom Actions, Commit and add a pointer to the SQL Server 
>>> Express MSI - custom actions in this section run at the end of the main 
>>> installation routine...
>>>
>>
>> i tried that, but it doesn't work. my main setup MSI is calls the SQL MSI 
>> from the commit action, but the SQL MSI gives me an error message about 
>> "Another installation is already in progress". any other ideas?
>
> Hmm - apologies, but I think you may be out of luck, as discussed here: 
> http://community.installshield.com/archive/index.php?t-155357.html
>


yes, i was afraid of that. i think i've got 2 options here:

1. write a parent installer that calls first the setup MSI, waits for 
completion, and then calls the SQL MSI. the main issue with this is that 
ideally i'd want to write the parent installer in C++, which i don't know. 
if i write it in C# and the user doesn't have the required framework 
installed, there's no elegant way to offer the user the option of 
downloading .Net. the C# parent installer will simply fail whereas a C++ 
version would call the setup MSI which could gracefully check for the 
required framwork and offer to download.

2. add the SQL MSI as a job for execution to a windows job queue. does such 
a thing exist? i know i've seen some setup projects force a reboot of the 
system and then complete phase 2 of an installation. is there a way to do 
this but without the reboot requirement?

tks for the help.


>
> -- 
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net 
Date:Thu, 16 Aug 2007 17:40:53 GMT   Author:  

Re: best way to do a concurrent installation   
"Dica"  wrote in message 
news:F_%wi.98056$tB5.27219@edtnps90...


> tks for the help.



Apologies again, but I don't really think I know enough about this to be of 
much help - hopefully, somebody else will - Juan, Peter, Jon, Eliyahu et 
al...?

Alternatively, you might try posting at microsoft.public.vsnet.setup...


-- 
Mark Rae
ASP.NET MVP
http://www.markrae.net
Date:Thu, 16 Aug 2007 20:46:55 +0100   Author:  

Re: best way to do a concurrent installation   
On 16 Aug, 18:40, "Dica"  wrote:

> "Mark Rae [MVP]"  wrote in messagenews:e53buTC4HHA.1484@TK2MSFTNGP06.phx.gbl...
>
> > "Dica"  wrote in message
> >news:9Y_wi.98052$tB5.56079@edtnps90...
>
> >>> Go into Custom Actions, Commit and add a pointer to the SQL Server
> >>> Express MSI - custom actions in this section run at the end of the main
> >>> installation routine...
>
> >> i tried that, but it doesn't work. my main setup MSI is calls the SQL MSI
> >> from the commit action, but the SQL MSI gives me an error message about
> >> "Another installation is already in progress". any other ideas?
>
> > Hmm - apologies, but I think you may be out of luck, as discussed here:
> >http://community.installshield.com/archive/index.php?t-155357.html
>
> yes, i was afraid of that. i think i've got 2 options here:
>
> 1. write a parent installer that calls first the setup MSI, waits for
> completion, and then calls the SQL MSI. the main issue with this is that
> ideally i'd want to write the parent installer in C++, which i don't know.
> if i write it in C# and the user doesn't have the required framework
> installed, there's no elegant way to offer the user the option of
> downloading .Net. the C# parent installer will simply fail whereas a C++
> version would call the setup MSI which could gracefully check for the
> required framwork and offer to download.
>
> 2. add the SQL MSI as a job for execution to a windows job queue. does such
> a thing exist? i know i've seen some setup projects force a reboot of the
> system and then complete phase 2 of an installation. is there a way to do
> this but without the reboot requirement?
>
> tks for the help.
>
>
>
>
>
> > --
> > Mark Rae
> > ASP.NET MVP
> >http://www.markrae.net- Hide quoted text -
>
> - Show quoted text -


I'm not sure if this will be of use, but if you don't know C++, you
could always use VB6 to write a parent installer. That would get
around the framework dependency and it would only take a couple of
lines of code to shell each of the msi's.
Date:Fri, 17 Aug 2007 03:33:18 -0700   Author:  

Re: best way to do a concurrent installation   
"DeveloperX"  wrote in message 
news:1187346798.764859.36080@g4g2000hsf.googlegroups.com...

> On 16 Aug, 18:40, "Dica"  wrote:
>> "Mark Rae [MVP]"  wrote in 
>> messagenews:e53buTC4HHA.1484@TK2MSFTNGP06.phx.gbl...
>>
>> > "Dica"  wrote in message
>> >news:9Y_wi.98052$tB5.56079@edtnps90...
>>
>> >>> Go into Custom Actions, Commit and add a pointer to the SQL Server
>> >>> Express MSI - custom actions in this section run at the end of the 
>> >>> main
>> >>> installation routine...
>>
>> >> i tried that, but it doesn't work. my main setup MSI is calls the SQL 
>> >> MSI
>> >> from the commit action, but the SQL MSI gives me an error message 
>> >> about
>> >> "Another installation is already in progress". any other ideas?
>>
>> > Hmm - apologies, but I think you may be out of luck, as discussed here:
>> >http://community.installshield.com/archive/index.php?t-155357.html
>>
>> yes, i was afraid of that. i think i've got 2 options here:
>>
>> 1. write a parent installer that calls first the setup MSI, waits for
>> completion, and then calls the SQL MSI. the main issue with this is that
>> ideally i'd want to write the parent installer in C++, which i don't 
>> know.
>> if i write it in C# and the user doesn't have the required framework
>> installed, there's no elegant way to offer the user the option of
>> downloading .Net. the C# parent installer will simply fail whereas a C++
>> version would call the setup MSI which could gracefully check for the
>> required framwork and offer to download.
>>
>> 2. add the SQL MSI as a job for execution to a windows job queue. does 
>> such
>> a thing exist? i know i've seen some setup projects force a reboot of the
>> system and then complete phase 2 of an installation. is there a way to do
>> this but without the reboot requirement?
>>
>> tks for the help.
>>
>>
>>
>>
>>
>> > --
>> > Mark Rae
>> > ASP.NET MVP
>> >http://www.markrae.net- Hide quoted text -
>>
>> - Show quoted text -
>
> I'm not sure if this will be of use, but if you don't know C++, you
> could always use VB6 to write a parent installer.


yeah, i do know VB6 pretty well. i should have thought of that.

tks for the suggestion.

 That would get

> around the framework dependency and it would only take a couple of
> lines of code to shell each of the msi's.
> 
Date:Fri, 17 Aug 2007 13:17:36 GMT   Author:  

Re: best way to do a concurrent installation   
Hi, 
I am also facing the same type of problem in my installation.
I have created a window service installer which has some other exe too
and this way i have created the shortcut( in program files and desktop)
for this exe.
 Now i require to uninstall the previous version and install the new
version of this installer,but this time the installation path should be
different.
 the problem is as below 

1- i tried to install but the installation suceeed but now when i click
the sortcut to launch the application , its how again installation
progress that make me crazy and in last  say the specified service
already exist
( this indicate the previous service not removed properly)

2- i am trying to add an exe(which will remove the previous version
exclusively ) in custom action editor install action. My aim is first
uninstall previous and then new installation
but as soon as this ready to remove previous version i found the error
as "another version of installtion is progress " .. i have to cance the
uninstall this faild my job

if some one has face this kind of situation and got some trick plz
suggest

Lalit N dubey



*** Sent via Developersdex http://www.developersdex.com ***
Date:Sun, 19 Aug 2007 22:24:39 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us