|
|
You're in the
dotnet setup
group:want to get app.path
dotnet setup:
i have a setup project and have a custom install class where i have this method wich tries to find a file named X.txt which is in the same folder as the current msi (wich i double clicked). now i want to copy this X.txt to a location in C:\. For that i created the custom install action class and wrote a method, but i cant access the current directory if i use application.path or other methods to get the current directory. it always give me c:\windows\system32, which i think is logical as my setup calls msiexec.exe which is in the windows\system32 folder. is there any way to know where my msi exe is? -- Vivek Thakur (MCP)
If you've installed the file in the application folder in the setup project,
this is identified by the TARGETDIR property. So pass [TARGETDIR] into your custom action (via CustomActionData) and it will be the path to your directory. -- Phil Wilson [Microsoft MVP-Windows Installer] Definitive Guide to Windows Installer http://apress.com/book/bookDisplay.html?bID=280 [quoted text, click to view] "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message news:6674A6D8-893C-4D44-89FA-A1E735513E3D@microsoft.com... > hi, > > i have a setup project and have a custom install class where i have this > method wich tries to find a file named X.txt which is in the same folder > as > the current msi (wich i double clicked). > > now i want to copy this X.txt to a location in C:\. For that i created the > custom install action class and wrote a method, but i cant access the > current > directory if i use application.path or other methods to get the current > directory. it always give me c:\windows\system32, which i think is logical > as > my setup calls msiexec.exe which is in the windows\system32 folder. > > is there any way to know where my msi exe is? > -- > Vivek Thakur (MCP) > www.vivekthakur.com
Phil,
thanks for yr response, but i cant use targetdir here as i want to knw the path *before* i have installed my app. Also, its like, i have to read some files from the folder *where my setup is present*, and not from where it wud get installed. But i cant use app.path as it gives me the path of msiexec in system32 folder. please advise some way. thanks, -- Vivek Thakur (MCP) www.vivekthakur.com [quoted text, click to view] "Phil Wilson" wrote:
> If you've installed the file in the application folder in the setup project, > this is identified by the TARGETDIR property. So pass [TARGETDIR] into your > custom action (via CustomActionData) and it will be the path to your > directory. > -- > Phil Wilson > [Microsoft MVP-Windows Installer] > Definitive Guide to Windows Installer > http://apress.com/book/bookDisplay.html?bID=280 > > "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message > news:6674A6D8-893C-4D44-89FA-A1E735513E3D@microsoft.com... > > hi, > > > > i have a setup project and have a custom install class where i have this > > method wich tries to find a file named X.txt which is in the same folder > > as > > the current msi (wich i double clicked). > > > > now i want to copy this X.txt to a location in C:\. For that i created the > > custom install action class and wrote a method, but i cant access the > > current > > directory if i use application.path or other methods to get the current > > directory. it always give me c:\windows\system32, which i think is logical > > as > > my setup calls msiexec.exe which is in the windows\system32 folder. > > > > is there any way to know where my msi exe is? > > -- > > Vivek Thakur (MCP) > > www.vivekthakur.com > >
I think you're saying that you want to copy some files that are in the same
directory as your MSI file. If so, pass [SourceDir] into your CustomActionData - that's the location of your MSI file. -- Phil Wilson [MVP Windows Installer] ---- [quoted text, click to view] "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message news:5EFDE134-D93F-455C-A43A-9C5E44E8A07C@microsoft.com... > Phil, > > thanks for yr response, but i cant use targetdir here as i want to knw the > path *before* i have installed my app. Also, its like, i have to read some > files from the folder *where my setup is present*, and not from where it > wud > get installed. But i cant use app.path as it gives me the path of msiexec > in > system32 folder. > > please advise some way. > > thanks, > -- > Vivek Thakur (MCP) > www.vivekthakur.com > > > "Phil Wilson" wrote: > >> If you've installed the file in the application folder in the setup >> project, >> this is identified by the TARGETDIR property. So pass [TARGETDIR] into >> your >> custom action (via CustomActionData) and it will be the path to your >> directory. >> -- >> Phil Wilson >> [Microsoft MVP-Windows Installer] >> Definitive Guide to Windows Installer >> http://apress.com/book/bookDisplay.html?bID=280 >> >> "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message >> news:6674A6D8-893C-4D44-89FA-A1E735513E3D@microsoft.com... >> > hi, >> > >> > i have a setup project and have a custom install class where i have >> > this >> > method wich tries to find a file named X.txt which is in the same >> > folder >> > as >> > the current msi (wich i double clicked). >> > >> > now i want to copy this X.txt to a location in C:\. For that i created >> > the >> > custom install action class and wrote a method, but i cant access the >> > current >> > directory if i use application.path or other methods to get the current >> > directory. it always give me c:\windows\system32, which i think is >> > logical >> > as >> > my setup calls msiexec.exe which is in the windows\system32 folder. >> > >> > is there any way to know where my msi exe is? >> > -- >> > Vivek Thakur (MCP) >> > www.vivekthakur.com >> >> >>
Phil,
thanks a lot!! sometimes solutions can be so simple..but i am wondering why isnt this documented anywhere.?? i did alot of rnd for this and didnt get any useful thing..i got targetdir and assemblypath parameters but not sourcedir.. anyways is shud ve used my brains..lol.. thanks a lot once again.,., -- Vivek Thakur (MCP) www.vivekthakur.com [quoted text, click to view] "Phil Wilson" wrote:
> I think you're saying that you want to copy some files that are in the same > directory as your MSI file. If so, pass [SourceDir] into your > CustomActionData - that's the location of your MSI file. > -- > Phil Wilson [MVP Windows Installer] > ---- > "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message > news:5EFDE134-D93F-455C-A43A-9C5E44E8A07C@microsoft.com... > > Phil, > > > > thanks for yr response, but i cant use targetdir here as i want to knw the > > path *before* i have installed my app. Also, its like, i have to read some > > files from the folder *where my setup is present*, and not from where it > > wud > > get installed. But i cant use app.path as it gives me the path of msiexec > > in > > system32 folder. > > > > please advise some way. > > > > thanks, > > -- > > Vivek Thakur (MCP) > > www.vivekthakur.com > > > > > > "Phil Wilson" wrote: > > > >> If you've installed the file in the application folder in the setup > >> project, > >> this is identified by the TARGETDIR property. So pass [TARGETDIR] into > >> your > >> custom action (via CustomActionData) and it will be the path to your > >> directory. > >> -- > >> Phil Wilson > >> [Microsoft MVP-Windows Installer] > >> Definitive Guide to Windows Installer > >> http://apress.com/book/bookDisplay.html?bID=280 > >> > >> "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message > >> news:6674A6D8-893C-4D44-89FA-A1E735513E3D@microsoft.com... > >> > hi, > >> > > >> > i have a setup project and have a custom install class where i have > >> > this > >> > method wich tries to find a file named X.txt which is in the same > >> > folder > >> > as > >> > the current msi (wich i double clicked). > >> > > >> > now i want to copy this X.txt to a location in C:\. For that i created > >> > the > >> > custom install action class and wrote a method, but i cant access the > >> > current > >> > directory if i use application.path or other methods to get the current > >> > directory. it always give me c:\windows\system32, which i think is > >> > logical > >> > as > >> > my setup calls msiexec.exe which is in the windows\system32 folder. > >> > > >> > is there any way to know where my msi exe is? > >> > -- > >> > Vivek Thakur (MCP) > >> > www.vivekthakur.com > >> > >> > >> > >
Visual Studio setup projects are Windows Installer setups, and the
properties you can use are listed here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/property_reference.asp?frame=true -- Phil Wilson [Microsoft MVP-Windows Installer] [quoted text, click to view] "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message news:75BB15E7-B6A0-40B9-A0C6-CF7A3985764B@microsoft.com... > Phil, > > thanks a lot!! sometimes solutions can be so simple..but i am wondering > why > isnt this documented anywhere.?? i did alot of rnd for this and didnt get > any useful thing..i got targetdir and assemblypath parameters but not > sourcedir.. > > anyways is shud ve used my brains..lol.. > > thanks a lot once again.,., > -- > Vivek Thakur (MCP) > www.vivekthakur.com > > > "Phil Wilson" wrote: > >> I think you're saying that you want to copy some files that are in the >> same >> directory as your MSI file. If so, pass [SourceDir] into your >> CustomActionData - that's the location of your MSI file. >> -- >> Phil Wilson [MVP Windows Installer] >> ---- >> "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message >> news:5EFDE134-D93F-455C-A43A-9C5E44E8A07C@microsoft.com... >> > Phil, >> > >> > thanks for yr response, but i cant use targetdir here as i want to knw >> > the >> > path *before* i have installed my app. Also, its like, i have to read >> > some >> > files from the folder *where my setup is present*, and not from where >> > it >> > wud >> > get installed. But i cant use app.path as it gives me the path of >> > msiexec >> > in >> > system32 folder. >> > >> > please advise some way. >> > >> > thanks, >> > -- >> > Vivek Thakur (MCP) >> > www.vivekthakur.com >> > >> > >> > "Phil Wilson" wrote: >> > >> >> If you've installed the file in the application folder in the setup >> >> project, >> >> this is identified by the TARGETDIR property. So pass [TARGETDIR] into >> >> your >> >> custom action (via CustomActionData) and it will be the path to your >> >> directory. >> >> -- >> >> Phil Wilson >> >> [Microsoft MVP-Windows Installer] >> >> Definitive Guide to Windows Installer >> >> http://apress.com/book/bookDisplay.html?bID=280 >> >> >> >> "Vivek Thakur" <vivekatvivekthakur(donotspam)com> wrote in message >> >> news:6674A6D8-893C-4D44-89FA-A1E735513E3D@microsoft.com... >> >> > hi, >> >> > >> >> > i have a setup project and have a custom install class where i have >> >> > this >> >> > method wich tries to find a file named X.txt which is in the same >> >> > folder >> >> > as >> >> > the current msi (wich i double clicked). >> >> > >> >> > now i want to copy this X.txt to a location in C:\. For that i >> >> > created >> >> > the >> >> > custom install action class and wrote a method, but i cant access >> >> > the >> >> > current >> >> > directory if i use application.path or other methods to get the >> >> > current >> >> > directory. it always give me c:\windows\system32, which i think is >> >> > logical >> >> > as >> >> > my setup calls msiexec.exe which is in the windows\system32 folder. >> >> > >> >> > is there any way to know where my msi exe is? >> >> > -- >> >> > Vivek Thakur (MCP) >> >> > www.vivekthakur.com >> >> >> >> >> >> >> >> >>
Phil,
In another post you write ********* The difficulty is when you try to add [TARGETDIR] as well it no longer works. A CustomActionData that says /src=[SourceDir] /dst=[TARGETDIR] fails with the FileNotFoundException. The issue seems to be that internally, the project is generating a Windows Installer custom action that calls the embedded InstallUtil DLL, passing: /installtype=notransaction /action=install /LogFile= /src=[SourceDir] /dst=[TARGETDIR] "[#_01E5F33094CF446280D30C8F055503CE]" "[VSDFxConfigFile]" What happens is the the /src and /dst specs are in the middle of a logfile specification, which breaks. *************** Of course, if you want to copy files from the source to the target, you need to know both at the same time. One workaround that seems to work; 1. Do the normal [TARGETDIR] custom action in the override for the install class. While you are in there you can do your normal stuff. 2. In the Registry section, write the value of the [TARGETDIR] to the registry (create a new key for your app). 3. Add another custom action for the commit phase to get the [SourceDir] 4. In the override for the commit class retrieve the [TARGETDIR] from the registry, get the [SorceDir] from argument parameters. You now have everything you need to copy stuff from the msi source folder to the target folder. This is done in the commit phase instead of the install phase but who cares after wasting all this time trying to figure out how to do it at all <g>. This works but why does Microsoft make something that should be trivial so complicated <g>. Note the [SourceDir] only has a single "\" in the front if the source is a UNC path - just another gotcha.....
It's my impression that a lot of people have started using Visual Studio for
setups and (because of the .NET association) are writing custom actions in managed code. People who have been building MSI setups for years have been writing C++ custom actions because Windows Installer supports them natively. Managed custom actions are supported by a shim Dll that processes CustomActionData and parses it into context in installer classes. If I ask people why they want to have all that extra complication in their setups it's usually because they don't want to learn C++ or go back to it, but the issues you're having are a result, and this kind of thing: http://support.microsoft.com/default.aspx?scid=kb;en-us;555184 http://support.microsoft.com/default.aspx?scid=kb;en-us;906766 See also http://www.installsite.org/pages/en/msifaq/a/1044.htm -- Phil Wilson [Microsoft MVP-Windows Installer] [quoted text, click to view] "Russell Stevens" <rustyprogrammer@online.nospam> wrote in message news:eTKETtaWGHA.3972@TK2MSFTNGP02.phx.gbl... > Phil, > > In another post you write > > ********* > The difficulty is when you try to add [TARGETDIR] as well it no longer > works. A CustomActionData that says /src=[SourceDir] /dst=[TARGETDIR] > fails with the FileNotFoundException. The issue seems to be that > internally, the project is generating a Windows Installer custom action > that calls the embedded InstallUtil DLL, passing: > /installtype=notransaction /action=install /LogFile= /src=[SourceDir] > /dst=[TARGETDIR] "[#_01E5F33094CF446280D30C8F055503CE]" > "[VSDFxConfigFile]" > > What happens is the the /src and /dst specs are in the middle of a logfile > specification, which breaks. > *************** > > Of course, if you want to copy files from the source to the target, you > need to know both at the same time. One workaround that seems to work; > > 1. Do the normal [TARGETDIR] custom action in the override for the install > class. While you are in there you can do your normal stuff. > > 2. In the Registry section, write the value of the [TARGETDIR] to the > registry (create a new key for your app). > > 3. Add another custom action for the commit phase to get the [SourceDir] > > 4. In the override for the commit class retrieve the [TARGETDIR] from the > registry, get the [SorceDir] from argument parameters. You now have > everything you need to copy stuff from the msi source folder to the target > folder. This is done in the commit phase instead of the install phase but > who cares after wasting all this time trying to figure out how to do it at > all <g>. > > This works but why does Microsoft make something that should be trivial so > complicated <g>. Note the [SourceDir] only has a single "\" in the front > if the source is a UNC path - just another gotcha..... >
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 |