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

Cannot install VSIX with VS2015 #60

Closed
zpqrtbnk opened this issue Jul 22, 2015 · 6 comments
Closed

Cannot install VSIX with VS2015 #60

zpqrtbnk opened this issue Jul 22, 2015 · 6 comments
Assignees
Labels

Comments

@zpqrtbnk
Copy link
Collaborator

I have installed VS2015 RTM. Whenever I double-click Zbu.ModelsBuilder VSIX file, nothing happens. An exception is logged in the event logged about some UnauthorizedAccess exception being thrown when trying to open the VSIX installer log.

@zpqrtbnk zpqrtbnk added the type/bug Bug label Jul 22, 2015
@zpqrtbnk zpqrtbnk self-assigned this Jul 22, 2015
@zpqrtbnk
Copy link
Collaborator Author

Manually launch the VSIXinstaller.exe from \Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE - same issue unless I'm administrator and then it works. From the help menu that opens, we see that VSIX installer wants to create log files in %TEMP%.

Which is \Users\Stéphane... for me... Oh... now there's a \Users\St%C3%A9phane directory too, that was created when VS2015 was installed, and sure enough... the install logs are there. Give my user full permission on that directory...

... and now when I double-click the VSIX file, it works. So the issue is with VSIX installer that has an issue understanding the accent in my user directory. Damn damn damn.

@zpqrtbnk
Copy link
Collaborator Author

VSIX installer does something similar to new Uri(Path.GetTempPath()) and that creates an invalid path.
Write to: Path.Combine(Path.GetTempPath(), "test.txt") => works.
Write to: new Uri(new Uri(Path.GetTempPath()), "test.txt").AbsolutePath => fails.

@zpqrtbnk
Copy link
Collaborator Author

OK, that has to be a bug within the VSIX installer. What's strange is that the code does not seem to have change. Reported to MS...

@zpqrtbnk
Copy link
Collaborator Author

@ryanlewis
Copy link

FWIW, works for me and my standard ASCII home directory

@zpqrtbnk
Copy link
Collaborator Author

MS reported "We have fixed this bug and it will be available in our next update." on Connect on 08/08.
Closing.

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

No branches or pull requests

2 participants