Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested amendments to Readme.rd #4

Open
mklement0 opened this issue Jul 12, 2013 · 2 comments
Open

Suggested amendments to Readme.rd #4

mklement0 opened this issue Jul 12, 2013 · 2 comments

Comments

@mklement0
Copy link

Great tool, thanks for making it available.

To access the *.exe, I had to reference it by its full path, <solutiondir>\packages\WebConfigTransformRunner.*\Tools\WebConfigTransformRunner.exe.

Unless there's an easier option I'm missing, I suggest adding this information to the read-me to help less-experienced users (read: me).

@erichexter
Copy link
Owner

Did you run it from the nuget console in visual studio? Nuget should add
all tool folders to the path for the console. If it did not work can you
tell me what version of studio including the update and what version if the
nuget plugin your running?

On Friday, July 12, 2013, Michael Klement wrote:

Great tool, thanks for making it available.

To access the .exe, I had to reference it by its full path,
\packages\WebConfigTransformRunner.
\Tools\WebConfigTransformRunner.exe
.

Unless there's an easier option I'm missing, I suggest adding this
information to the read-me to help less-experienced users (read: me).


Reply to this email directly or view it on GitHubhttps://github.com//issues/4
.

Eric Hexter

blog | http://Hex.LosTechies.com
info | http://www.linkedin.com/in/erichexter

@mklement0
Copy link
Author

That's the easier option I missed - thanks. :)

Thus I suggest you add the following to the read-me:

  • From a NuGet console (in VS2012: Tools > Library Package Manager > Package Manager Console), you can run the tool simply by name - WebConfigTransformRunner
  • From a regular console window, you can invoke the tool by its path: <solutiondir>\packages\WebConfigTransformRunner.*\Tools\WebConfigTransformRunner.exe
  • Alternatively, if you want to make the tool available globally (in a solution-independent manner), copy the following files to a folder in your %PATH%:
    • <solutiondir>\packages\WebConfigTransformRunner.*\Tools\WebConfigTransformRunner.exe
    • <solutiondir>\packages\WebConfigTransformRunner.*\Tools\Microsoft.Web.XmlTransform.dll

Finally - and I realize that it's probably too late to do this - you could shorten the name a little to WebConfigTransfomer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants