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

Property page doesn't load #267

Closed
LegalizeAdulthood opened this Issue Apr 19, 2016 · 10 comments

Comments

Projects
None yet
2 participants
@LegalizeAdulthood

LegalizeAdulthood commented Apr 19, 2016

image

Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2
Microsoft .NET Framework
Version 4.6.01055

Installed Version: Community

Visual Basic 2015 00322-20000-00000-AA493
Microsoft Visual Basic 2015

Visual C# 2015 00322-20000-00000-AA493
Microsoft Visual C# 2015

Visual C++ 2015 00322-20000-00000-AA493
Microsoft Visual C++ 2015

Application Insights Tools for Visual Studio Package 5.2.60328.3
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET and Web Tools 2015.1 (Beta8)

ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET Web Frameworks and Tools 2013 5.2.40314.0
For additional information, visit http://www.asp.net/

Atomineer Pro Documentation 1.0
Source-code documentation-comment creation and maintenance, and other documentation-related tools.

Clang with Microsoft CodeGen 14.0.25115
Clang with Microsoft CodeGen

Common Azure Tools 1.7
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

GitHub.VisualStudio 1.0
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.

JavaScript Language Service 2.0
JavaScript Language Service

JavaScript Project System 2.0
JavaScript Project System

JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper. Copyright © 2016 JetBrains, Inc.

Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools

Node.js Tools 1.1.31117.00
Adds support for developing and debugging Node.js apps in Visual Studio

Node.js Tools - Profiling 1.1.31117.00
Profiling support for Node.js projects.

NuGet Package Manager 3.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools 14.0.60311.1
Microsoft SQL Server Data Tools

TypeScript 1.8.29.0
TypeScript tools for Visual Studio

VisualHG 1.1.7
Mercurial source contol provider.

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 19, 2016

Collaborator

Thanks for reporting this!

@mponce1 @donokuda Can you repro this?

Collaborator

shana commented Apr 19, 2016

Thanks for reporting this!

@mponce1 @donokuda Can you repro this?

@LegalizeAdulthood

This comment has been minimized.

Show comment
Hide comment
@LegalizeAdulthood

LegalizeAdulthood Apr 19, 2016

Does it display anything normally?

Does it display anything normally?

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 19, 2016

Collaborator

It should display a checkbox, yes.

What is the version on the extension you have installed (from Tools / Extensions and Updates)?

Also, can you run VS with the activity log on (devenv /log in the VS 2015 Developer Prompt command line) and post the log to a gist (or send it to support@github.com with a link to this issue if there's anything in there you'd rather keep private)

Collaborator

shana commented Apr 19, 2016

It should display a checkbox, yes.

What is the version on the extension you have installed (from Tools / Extensions and Updates)?

Also, can you run VS with the activity log on (devenv /log in the VS 2015 Developer Prompt command line) and post the log to a gist (or send it to support@github.com with a link to this issue if there's anything in there you'd rather keep private)

@LegalizeAdulthood

This comment has been minimized.

Show comment
Hide comment
@LegalizeAdulthood

LegalizeAdulthood Apr 19, 2016

I pasted the information from the about box above, it says:

GitHub.VisualStudio 1.0
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.

I pasted the information from the about box above, it says:

GitHub.VisualStudio 1.0
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.

@LegalizeAdulthood

This comment has been minimized.

Show comment
Hide comment
@LegalizeAdulthood

LegalizeAdulthood Apr 19, 2016

Tools / Extensions and Updates says 1.0.18.1

Tools / Extensions and Updates says 1.0.18.1

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 19, 2016

Collaborator

There should be 1.0.18.2 available, but before you update, if you could run VS with logging enabled so I can check what's up, that'd be great. There's nothing in 1.0.18.2 that relates to the property pages, so if it starts working after you update, it's a sign of some sort of corruption in VS or the extension installation.

Collaborator

shana commented Apr 19, 2016

There should be 1.0.18.2 available, but before you update, if you could run VS with logging enabled so I can check what's up, that'd be great. There's nothing in 1.0.18.2 that relates to the property pages, so if it starts working after you update, it's a sign of some sort of corruption in VS or the extension installation.

@LegalizeAdulthood

This comment has been minimized.

Show comment
Hide comment
@LegalizeAdulthood

LegalizeAdulthood Apr 21, 2016

Not sure how to run with logging, but if you tell me what to do, I can follow instructions 😸

Not sure how to run with logging, but if you tell me what to do, I can follow instructions 😸

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 21, 2016

Collaborator

Alrighty then! rolls up sleeves

  1. Close Visual Studio if it's open
  2. Open a Developer Command Prompt for VS2015
  3. Run devenv /log
  4. Go to the property page that's failing
  5. Close VS
  6. The log is at %appdata%\Microsoft\VisualStudio\14.0\ActivityLog.xml. Grab that and send it to shana at github dot com. While you're at it, send the %localappdata%\temp\extension.log file, too.
Collaborator

shana commented Apr 21, 2016

Alrighty then! rolls up sleeves

  1. Close Visual Studio if it's open
  2. Open a Developer Command Prompt for VS2015
  3. Run devenv /log
  4. Go to the property page that's failing
  5. Close VS
  6. The log is at %appdata%\Microsoft\VisualStudio\14.0\ActivityLog.xml. Grab that and send it to shana at github dot com. While you're at it, send the %localappdata%\temp\extension.log file, too.
@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 27, 2016

Collaborator

Found the problem! We'll have a fix out in the next release asap.

Collaborator

shana commented Apr 27, 2016

Found the problem! We'll have a fix out in the next release asap.

shana added a commit that referenced this issue Apr 28, 2016

Make sure our assembly resolver always runs
Fixes #267

For some reason, the xaml loader fails miserably when trying to resolve
where to load our DLLs from if they're not yet in the process. The
directories it's scanning don't include the extension installation path,
so it can't find any assemblies that are referenced directly from xaml
(using types from other assemblies in code works fine, using them in
xaml doesn't).
We have an assembly resolver code path as part of our ResourceDictionary
implementation (SharedDictionaryManager), so every xaml user control
needs to have at least one include that uses SharedDictionaryManager in
order to trigger the assembly resolver hook up and ensure that libraries
are found.
@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Apr 28, 2016

Collaborator

To repro this is to set Solution Explorer as the focused pane and then restart VS, so that the next time it starts up it doesn't load Team Explorer by default (which means our assemblies won't get loaded beyond just the package initialization). Then go to Tools / Options and try to load the GitHub property page. It fails miserably.

@mponce1 Probably worth adding this to our test manifest 😛

Collaborator

shana commented Apr 28, 2016

To repro this is to set Solution Explorer as the focused pane and then restart VS, so that the next time it starts up it doesn't load Team Explorer by default (which means our assemblies won't get loaded beyond just the package initialization). Then go to Tools / Options and try to load the GitHub property page. It fails miserably.

@mponce1 Probably worth adding this to our test manifest 😛

@shana shana added bug verified labels May 2, 2016

mponce1 added a commit that referenced this issue May 4, 2016

267 Manifest inUpdate
Update manifest to include case for #267

@Haacked Haacked closed this in #272 May 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment