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

Revit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI #7

Closed
chuongmep opened this issue Jan 25, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@chuongmep
Copy link
Owner

Describe the bug
Revit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI '/RevitAddinManager;component/view/frmaddinmanager.xaml'.
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at RevitAddinManager.View.FrmAddInManager..ctor(AddInManagerViewModel vm)
at RevitAddinManager.Command.AddinManagerBase.ExecuteCommand(ExternalCommandData data, String& message, ElementSet elements, Boolean faceless)
at RevitAddinManager.Command.AddInManagerManual.Execute(ExternalCommandData commandData, String& message, ElementSet elements)
at apiManagedExecuteCommand(AString* assemblyName, AString* className, AString* vendorDescription, MFCApp* pMFCApp, DBView* pDBView, AString* message, Set<ElementId,std::less,tnallc >* ids, Map<AString,AString,std::less,tnallc<std::pair<AString const ,AString> > >* data, AString* exceptionName, AString* exceptionMessage)

To Reproduce
Steps to reproduce the behavior:

  1. Go to Addin Open Add-in Manager
  2. Click Load dll Add-in manager to Add-in Manager
  3. Run AddinManager loaded
  4. Open again Add-in Manager from ribbon
  5. See Error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser [e.g. chrome, safari]
  • Version Revit 2023
@chuongmep
Copy link
Owner Author

If you agree to this, the load assemblies will be duplicated, causing them not to recognize the correct paths

@chuongmep chuongmep changed the title evit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI Revit encountered a System.Exception: The component 'RevitAddinManager.View.FrmAddInManager' does not have a resource identified by the URI Feb 23, 2022
@chuongmep
Copy link
Owner Author

@chuongmep
Copy link
Owner Author

System.InvalidCastException: [A]RevitAddinManager.View.Control.ExtendedTreeView cannot be cast to [B]RevitAddinManager.View.Control.ExtendedTreeView. Type A originates from 'RevitAddinManager, Version=2022.0.0.0, Culture=neutral, PublicKeyToken=null' in the context 'LoadNeither' at location 'C:\Users\Chuong.Ho\AppData\Local\Temp\RevitAddins\RevitAddinManager-Executing-20220529_151417_2606\RevitAddinManager.dll'. Type B originates from 'RevitAddinManager, Version=2023.0.0.0, Culture=neutral, PublicKeyToken=null' in the context 'LoadFrom' at location 'C:\Users\Chuong.Ho\AppData\Roaming\Autodesk\Revit\Addins\2023\RevitAddinManager\RevitAddinManager.dll'.
at RevitAddinManager.View.FrmAddInManager.System.Windows.Markup.IComponentConnector.Connect(Int32 connectionId, Object target) in D:\API\Revit\RevitAddInManager\AddInManager\View\FrmAddInManager.xaml:line 0
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetConnectionId(Object root, Int32 connectionId, Object instance)

@chuongmep
Copy link
Owner Author

dotnet/wpf#1700

@chuongmep
Copy link
Owner Author

dotnet/wpf#4494

@lishuangquan1987
Copy link

@chuongmep Do you have found the root cause of this problem?

https://chowdera.com/2022/03/202203091902109000.html

this is written by me. It seems that there are lots of wpf problems in .Net6,especially in plugin-architecture application,which makes me want to change to .Net4.7.2

@chuongmep
Copy link
Owner Author

chuongmep commented Jun 15, 2022

@lishuangquan1987 still not yet, it problem from core of wpf, error same when change to in net 4.7.2, you can read some acticle has reported in main github wpf open source in dotnet/wpf#1700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants