By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,168 Members | 2,598 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,168 IT Pros & Developers. It's quick & easy.

.NET - Package and Deployment Project - What's the dilio?

P: n/a

Here's my situation: I'm designing a package and deployment project and
I've created a new custom folder. Here is what I have so far:

Application Folder (TARGETDIR): [program files]\sql server\mssql\reporting
Custom Folder 1 (CUSTOMPATH): [TARGETDIR]\bin\

The application folder has the default variable of "TARGETDIR" so I can use
that in my path for "Custom Folder 1".

On a default install where I don't change the application folder path, I get
a path of "C:\Program Files\sql server\mssql\reporting services\bin\" for
the "TARGETDIR", but when I change the application folder, the TARGETDIR
does not reflect that change, it stays set to the default path.

Has anyone else encountered this and been able to workaround it?
Essentially, all I'm trying to do is install some additional files into the
bin folder which is one folder above the install folder.

Surely there's a way to do this with the package and deployment capabilities
in VS.NET.

Any help would be greatly appreciated!


Benjamin Pierce
Open Text Corporation

Nov 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.