[#NEO-58] Setup fails to initialize the Visual Studio Custom Tool

Neo

Setup fails to initialize the Visual Studio Custom Tool

Created: 20/Apr/06 03:05 PM Updated: 01/Jun/06 09:18 AM

Component/s:

Tools

Affects Version/s:

1.4.0

Fix Version/s:

1.4.2

Time Tracking:

Not Specified

Environment:

Visual Studio 2003

Description

« Hide

Run Custom Tool on the schema file does not work after running the setup. We have to perform the steps as implemented in setup.bat manually, or run setup.bat manually.

It's natural to expect a setup to configure a complete, runnable environment. In this case we have to hunt down the setup.bat file from the zipped source.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Erik Doernenburg - 24/Apr/06 05:44 PM

I've tried and I cannot reproduce it. In my environment the tool is correctly configured after the installer was run. Also, I am quite sure that other people have used this and so far nobody seems to have problems.

Is there anything special in your environment? Did you try to set up Neo 'for all users' or just for yourself? I'm asking because I suspect that you might not have access rights to the registry for all users. When you run the bat file, it'll only write it for you. Could you try this?

[ Permlink | « Hide ]

Thomas Eyde - 25/Apr/06 05:35 AM

I did setup just for me, I guess. I didn't touch the default settings
and 'Just me' is usually the default.

I am also the only user on my laptop.

Now that it is working, which steps do I need to take to completely uninstall?

[ Permlink | « Hide ]

Erik Doernenburg - 26/Apr/06 08:52 AM

Turns out this is a problem which must have been masked by previous installs. The MSI installer does not use regasm to register the VS tool.

[ Permlink | « Hide ]

Erik Doernenburg - 01/Jun/06 09:18 AM

Turns out this was caused by a VisualStudio bug. I've now added the workaround described here:

http://www.dotnet247.com/247reference/msgs/46/231535.aspx