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

Visual Studio 2015 CTP 6 : An error occurred trying to load the project properties window #39

Closed
jaliyaudagedara opened this Issue Apr 23, 2015 · 20 comments

Comments

Projects
None yet
@jaliyaudagedara

jaliyaudagedara commented Apr 23, 2015

When opening project properties of any project (MVC, Web API, Class Library, Console Application etc.) created targeting ASP.NET 5, I am getting this error.

"An error occurred trying to load the project properties window. Close the window and try again. COM object that has been separated from its underlying RCW cannot be used."

2015-04-23_20-01-13

Any ideas?

@jaliyaudagedara jaliyaudagedara changed the title from Visual Studio 2015 CTP 6 ASP.NET Project Properties : An error occurred trying to load the project properties window to Visual Studio 2015 CTP 6 : An error occurred trying to load the project properties window Apr 23, 2015

@BillHiebert

This comment has been minimized.

Show comment
Hide comment
@BillHiebert

BillHiebert Apr 23, 2015

Can you use a newer build than CTP6?

BillHiebert commented Apr 23, 2015

Can you use a newer build than CTP6?

@jaliyaudagedara

This comment has been minimized.

Show comment
Hide comment
@jaliyaudagedara

jaliyaudagedara Apr 30, 2015

Issue was present in Visual Studio 2015 RC as well. Contacted Microsoft and the issue was with the GhostDoc VS Extension. Unloaded GhostDoc VS Extension from Visual Studio 2015 RC, and the problem got resolved.

Thank you Microsoft!

jaliyaudagedara commented Apr 30, 2015

Issue was present in Visual Studio 2015 RC as well. Contacted Microsoft and the issue was with the GhostDoc VS Extension. Unloaded GhostDoc VS Extension from Visual Studio 2015 RC, and the problem got resolved.

Thank you Microsoft!

@RehanSaeed

This comment has been minimized.

Show comment
Hide comment
@RehanSaeed

RehanSaeed Jun 22, 2015

Thanks @jaliyaudagedara. I can confirm GhostDoc was the problem. I have emailed them a link to this thread.

RehanSaeed commented Jun 22, 2015

Thanks @jaliyaudagedara. I can confirm GhostDoc was the problem. I have emailed them a link to this thread.

@sergebee

This comment has been minimized.

Show comment
Hide comment
@sergebee

sergebee Jun 22, 2015

Rehan,

Thank you for bringing the thread to our attention!

Yes, we were aware of this and already resolved it. We have a private build of GhostDoc that includes the fix.

Thanks!

sergebee commented Jun 22, 2015

Rehan,

Thank you for bringing the thread to our attention!

Yes, we were aware of this and already resolved it. We have a private build of GhostDoc that includes the fix.

Thanks!

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Aug 10, 2015

@sergebee - Any updates on this? I recently encountered the same thing (#138), also caused by GhostDoc.

Daniel15 commented Aug 10, 2015

@sergebee - Any updates on this? I recently encountered the same thing (#138), also caused by GhostDoc.

@SergeBaranovsky

This comment has been minimized.

Show comment
Hide comment
@SergeBaranovsky

SergeBaranovsky Aug 13, 2015

@Daniel15 - drop us a note at support at submain dot com and tell which edition you need - we will provide you with download link.

Thanks!

SergeBaranovsky commented Aug 13, 2015

@Daniel15 - drop us a note at support at submain dot com and tell which edition you need - we will provide you with download link.

Thanks!

@Daniel15

This comment has been minimized.

Show comment
Hide comment
@Daniel15

Daniel15 Aug 13, 2015

Thanks @SergeBaranovsky, I sent an email

Daniel15 commented Aug 13, 2015

Thanks @SergeBaranovsky, I sent an email

@BillKrat

This comment has been minimized.

Show comment
Hide comment
@BillKrat

BillKrat Oct 17, 2015

Issue also breaking Visual Studio publish; I click on the publish button and nothing happens - I thought it had to do with beta8 but once I uninstalled GhostDoc to eliminate the error addressed here my publish feature started working.

BillKrat commented Oct 17, 2015

Issue also breaking Visual Studio publish; I click on the publish button and nothing happens - I thought it had to do with beta8 but once I uninstalled GhostDoc to eliminate the error addressed here my publish feature started working.

@RehanSaeed

This comment has been minimized.

Show comment
Hide comment
@RehanSaeed

RehanSaeed Oct 18, 2015

Is this still broken in the latest version. I quite liked GhostDoc.

RehanSaeed commented Oct 18, 2015

Is this still broken in the latest version. I quite liked GhostDoc.

@BillKrat

This comment has been minimized.

Show comment
Hide comment
@BillKrat

BillKrat Oct 18, 2015

It is with Visual Studio 2015 beta 8. I sent them an email and have a support ticket. I could have lived with the com error (I like GhostDoc that much) but can't live with the publish issue...

BillKrat commented Oct 18, 2015

It is with Visual Studio 2015 beta 8. I sent them an email and have a support ticket. I could have lived with the com error (I like GhostDoc that much) but can't live with the publish issue...

@BillHiebert

This comment has been minimized.

Show comment
Hide comment
@BillHiebert

BillHiebert Oct 19, 2015

This is a known issue in GhostDoc. They released an update available here: http://submain.com/Download/NightlyBuild/gd_4.9.15168.zip

BillHiebert commented Oct 19, 2015

This is a known issue in GhostDoc. They released an update available here: http://submain.com/Download/NightlyBuild/gd_4.9.15168.zip

@SergeBaranovsky

This comment has been minimized.

Show comment
Hide comment
@SergeBaranovsky

SergeBaranovsky Oct 19, 2015

Bill, thank you for posting the link. Yes, that build addresses the issue although now is pretty early build and we are about the release v5 that addresses this issue as well. If you want a pre-release build, drop us a note at support at submain dot com. Thanks for your patience!

SergeBaranovsky commented Oct 19, 2015

Bill, thank you for posting the link. Yes, that build addresses the issue although now is pretty early build and we are about the release v5 that addresses this issue as well. If you want a pre-release build, drop us a note at support at submain dot com. Thanks for your patience!

@lismore

This comment has been minimized.

Show comment
Hide comment
@lismore

lismore Nov 3, 2015

Hi guys,

I find this same issue in the latest version of VS 2015 (Pro)
image

lismore commented Nov 3, 2015

Hi guys,

I find this same issue in the latest version of VS 2015 (Pro)
image

@zemien

This comment has been minimized.

Show comment
Hide comment
@zemien

zemien Nov 25, 2015

@lismore I had to restart Visual Studio after unloading GhostDoc. I can now open Project Properties.

I have VS Enterprise 2015 Update 1 RC, and ASP.Net 5 RC1.

zemien commented Nov 25, 2015

@lismore I had to restart Visual Studio after unloading GhostDoc. I can now open Project Properties.

I have VS Enterprise 2015 Update 1 RC, and ASP.Net 5 RC1.

@SergeBaranovsky

This comment has been minimized.

Show comment
Hide comment
@SergeBaranovsky

SergeBaranovsky Nov 25, 2015

@ALL,

We have made a new GhostDoc update available yesterday and it includes the fix. Please download the new bits from http://submain.com/ghostdoc - thank you for the patience!

SergeBaranovsky commented Nov 25, 2015

@ALL,

We have made a new GhostDoc update available yesterday and it includes the fix. Please download the new bits from http://submain.com/ghostdoc - thank you for the patience!

@rlvandaveer

This comment has been minimized.

Show comment
Hide comment
@rlvandaveer

rlvandaveer Dec 3, 2015

@SergeBaranovsky While that's great that you've fixed it in v5, the latest version of v4 has this issue.

rlvandaveer commented Dec 3, 2015

@SergeBaranovsky While that's great that you've fixed it in v5, the latest version of v4 has this issue.

@SergeBaranovsky

This comment has been minimized.

Show comment
Hide comment
@SergeBaranovsky

SergeBaranovsky Dec 3, 2015

@rlvandaveer I'm not sure what the problem is... Upgrade to the v5?

SergeBaranovsky commented Dec 3, 2015

@rlvandaveer I'm not sure what the problem is... Upgrade to the v5?

@rlvandaveer

This comment has been minimized.

Show comment
Hide comment
@rlvandaveer

rlvandaveer Dec 3, 2015

This is probably not the right forum for this (sorry aspnet/tooling folks) but I thought that SubMain's v4 clients that find this thread (and possibly SubMain) might want to know that barring paying for the next version, there is no fix.

rlvandaveer commented Dec 3, 2015

This is probably not the right forum for this (sorry aspnet/tooling folks) but I thought that SubMain's v4 clients that find this thread (and possibly SubMain) might want to know that barring paying for the next version, there is no fix.

@SergeBaranovsky

This comment has been minimized.

Show comment
Hide comment
@SergeBaranovsky

SergeBaranovsky Dec 3, 2015

You are correct, this is not the right forum for that. (sorry aspnet/tooling folks) Users of the free GhostDoc still get their v5 upgrade free, the commercial license users who chose to be getting updates via the software assurance subscription, also get the v5 version free.

If you want to continue the discussion, please take it to SubMain forums or offline via email. Thanks!

SergeBaranovsky commented Dec 3, 2015

You are correct, this is not the right forum for that. (sorry aspnet/tooling folks) Users of the free GhostDoc still get their v5 upgrade free, the commercial license users who chose to be getting updates via the software assurance subscription, also get the v5 version free.

If you want to continue the discussion, please take it to SubMain forums or offline via email. Thanks!

@BNarayanSharma

This comment has been minimized.

Show comment
Hide comment
@BNarayanSharma

BNarayanSharma Feb 13, 2016

I was also facing the same issue in Visual Studio 2015. I was using GhostDoc Community 4.9.x and I upgraded it to 5.1.x and issue get resolved.

BNarayanSharma commented Feb 13, 2016

I was also facing the same issue in Visual Studio 2015. I was using GhostDoc Community 4.9.x and I upgraded it to 5.1.x and issue get resolved.

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