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

Unable to cast transparent proxy to type 'WixExtensionValidator' 3.11 #5726

Open
arparadhya opened this Issue Nov 24, 2017 · 15 comments

Comments

Projects
None yet
7 participants
@arparadhya

arparadhya commented Nov 24, 2017

Please provide answers to the following questions to help us narrow down, reproduce, and fix the problem. Fill out one section and delete the others.

Triage

Issues are triaged at online meetings, generally held alternate Tuesdays at 9:30 a.m. Pacific time (UTC-7/UTC-8). Meeting requests are sent to the wix-devs mailing list.

Discussions and support

I 'm unable to add reference to Wix Setup project. I get 'Unable to cast transparent proxy to type 'WixExtensionValidator' when I add the extension on to the project.

Bugs

If this issue is a bug:

  • Which version of WiX are you building with?

Wix 3.11

  • Which version of Visual Studio are you building with (if any)?

Visual Studio 2017 Community

  • Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?

Wix V3.

  • Which version of .NET are you building with?

4.6.1

  • If the problem occurs when installing your packages built with WiX, what is the version of Windows the package is running on?

Windows 10 64 bit home

  • Describe the problem and the steps to reproduce it.

Create a new Setup Project Wix V3 to an existing project
Try to add reference like the extensions from Bin folder of Wix 3.11 to the reference

  • Describe the behavior you expected and how it differed from the actual behavior.

It should allow to easily add the reference.
error

@barnson

This comment has been minimized.

Show comment
Hide comment
@barnson

barnson Nov 30, 2017

Member

What are the full (four-part) version numbers of VS, WiX, and the WiX VS extension?

Member

barnson commented Nov 30, 2017

What are the full (four-part) version numbers of VS, WiX, and the WiX VS extension?

@arparadhya

This comment has been minimized.

Show comment
Hide comment
@arparadhya

arparadhya Dec 1, 2017

arparadhya commented Dec 1, 2017

@barnson

This comment has been minimized.

Show comment
Hide comment
@barnson

barnson Dec 1, 2017

Member

We're looking for the exact version numbers, like WiX v3.11.0.1528 or extension 0.9.21.62588.

Member

barnson commented Dec 1, 2017

We're looking for the exact version numbers, like WiX v3.11.0.1528 or extension 0.9.21.62588.

@paj777

This comment has been minimized.

Show comment
Hide comment
@paj777

paj777 Dec 13, 2017

Hi, I have the exact same issue as above and I have the extension 0.9.21.62588. Is there a solution to this issue?

paj777 commented Dec 13, 2017

Hi, I have the exact same issue as above and I have the extension 0.9.21.62588. Is there a solution to this issue?

@barnson

This comment has been minimized.

Show comment
Hide comment
@barnson

barnson Dec 13, 2017

Member

What version of WiX? What version of Visual Studio?

Member

barnson commented Dec 13, 2017

What version of WiX? What version of Visual Studio?

@paj777

This comment has been minimized.

Show comment
Hide comment
@paj777

paj777 Dec 13, 2017

Exactly as described above. VS 2017 and WiX 3.11. So despite the error messages, if you close Visual Studio and reopen the references are there and working fine.

paj777 commented Dec 13, 2017

Exactly as described above. VS 2017 and WiX 3.11. So despite the error messages, if you close Visual Studio and reopen the references are there and working fine.

@barnson

This comment has been minimized.

Show comment
Hide comment
@barnson

barnson Dec 13, 2017

Member

We're looking for the full version numbers. There are many releases of VS 2017 and WiX v3.11 and we haven't seen this behavior with the latest.

Member

barnson commented Dec 13, 2017

We're looking for the full version numbers. There are many releases of VS 2017 and WiX v3.11 and we haven't seen this behavior with the latest.

@paj777

This comment has been minimized.

Show comment
Hide comment
@paj777

paj777 Dec 14, 2017

Visual studio Professional 2017 version 15.4.4 and, as stated above, Wix Toolset for Visual Studio 2017 Extension version 0.9.21.62588.

paj777 commented Dec 14, 2017

Visual studio Professional 2017 version 15.4.4 and, as stated above, Wix Toolset for Visual Studio 2017 Extension version 0.9.21.62588.

@barnson barnson added this to the v4.0 milestone Dec 14, 2017

@macgyver76

This comment has been minimized.

Show comment
Hide comment
@macgyver76

macgyver76 Jan 3, 2018

Any updates on this one?

macgyver76 commented Jan 3, 2018

Any updates on this one?

@robmen

This comment has been minimized.

Show comment
Hide comment
@robmen

robmen Jan 3, 2018

Member

This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution.

If you are interested in doing so yourself, our developer documentation provides a great checklist for getting started.

If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options.

Member

robmen commented Jan 3, 2018

This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution.

If you are interested in doing so yourself, our developer documentation provides a great checklist for getting started.

If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options.

@paj777

This comment has been minimized.

Show comment
Hide comment
@paj777

paj777 Jan 4, 2018

After I got these errors, I later noticed, after a Visual Studio restart the references had in fact been added anyway.

paj777 commented Jan 4, 2018

After I got these errors, I later noticed, after a Visual Studio restart the references had in fact been added anyway.

@macgyver76

This comment has been minimized.

Show comment
Hide comment
@macgyver76

macgyver76 Jan 4, 2018

@paj777 I need to check this as well. Thanks.

macgyver76 commented Jan 4, 2018

@paj777 I need to check this as well. Thanks.

@macgyver76

This comment has been minimized.

Show comment
Hide comment
@macgyver76

macgyver76 Jan 5, 2018

@paj777 After reinstalling WixTools, everything works fine.

macgyver76 commented Jan 5, 2018

@paj777 After reinstalling WixTools, everything works fine.

@bleppard

This comment has been minimized.

Show comment
Hide comment
@bleppard

bleppard Mar 20, 2018

I am experience the same symptoms. After Visual Studio restart, the reference to the extension was there.

Full version strings:

  • Visual Studio 15.6.0 - 15.6.27428.1
  • WiX Toolset v3.11.0.1701
  • WiX Toolset Visual Studio Extension version 0.9.21.62588

bleppard commented Mar 20, 2018

I am experience the same symptoms. After Visual Studio restart, the reference to the extension was there.

Full version strings:

  • Visual Studio 15.6.0 - 15.6.27428.1
  • WiX Toolset v3.11.0.1701
  • WiX Toolset Visual Studio Extension version 0.9.21.62588
@PerssonRobert

This comment has been minimized.

Show comment
Hide comment
@PerssonRobert

PerssonRobert Apr 20, 2018

Another solution instead of restarting VS after the error is to unload the setupproject and then reload it, voila, the references are there.

PerssonRobert commented Apr 20, 2018

Another solution instead of restarting VS after the error is to unload the setupproject and then reload it, voila, the references are there.

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