DevExpress Assembly Deployment Tool - The "Analyze" button is disabled if the tool is started using VS 2022
Answers approved by DevExpress Support
We have addressed the issue described in this ticket and will include a fix in our next maintenance update. Should you need to apply our fix prior to official release, you can request a hotfix here.
Important Notes:
- Hotfixes may be unavailable for Early Access/Beta builds or updates set for release within a week.
- .NET only: in the NuGet Package Manager, use your personal NuGet feed and check the "Include prerelease" option to view the hotfix package in the "Updates" tab.
- v22.1.3Download Official Update
- v21.2.5Download Official Update
Hello,
Thank you for your inquiry. I was able to replicate the same behavior on my side. It seems that the Deployment tool cannot find projects to deploy in the new Visual Studio 2022 and, as a result, the Analyze button is disabled. Our R&D team will review this support ticket. Once we know more, I'll follow up with you here.
Thanks,
Michael
Maybe you can give me some workaround, our project moved to net6, thus and we can't use 2017 studio only 2022.
We need to make assembly to deploy, but can't.
Hi,
is there already a solution in sight?
Would be nice…
Peter
Yes. A solution from DevExpress would be nice. Or should we try to create our own own solution?
We don't have a workaround. You can use a built-in Visual Studio deployment feature like ClickOnce.
Okay. One more question where can I find a list of dependencies?
For example, if a web application references a specific dll inside web.config or the page itself. Where can i find ALL dependencies the specific dll may require?
I've create a tool using Microsoft Visual Basic and I just need a way to insure ALL dlls are being uploaded.
Hello Ray,
You can find a list of redistributable assemblies in the following help topic:
ASP.NET - Redistribution and Deployment.
Note that we also have corresponding topics for other platforms:
WPF - Redistribution and Deployment,
WinForms - Redistribution and Deployment.
Let me know if you have additional questions.
Thanks! This is what I need.
Should I only have to upload the dlls referenced in the web.config? Are there any other places i need to check to make sure I get all of them?
<assemblies>
<add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="DevExpress.Web.ASPxThemes.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" />
<add assembly="DevExpress.Data.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.Web.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="System.Web.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="DevExpress.Printing.v21.2.Core, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.Office.v21.2.Core, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.RichEdit.v21.2.Core, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.Web.ASPxHtmlEditor.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.Web.ASPxSpellChecker.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.SpellChecker.v21.2.Core, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.Web.ASPxScheduler.v21.2, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.XtraScheduler.v21.2.Core, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" />
<add assembly="DevExpress.XtraScheduler.v21.2.Core.Desktop, Version=21.2.3.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A" /></assemblies>
Ray,
I recommend using the built-in wizard for publishing a project to identify all necessary assemblies.
What should I do? I have the same problem.
I've the same issue also with 21.2.4. I hoped you solved this issue.
Do you have any update?
Thanks
I went back to my VS2019 VM and did a deploy. Since the libraries for DevExpress do not change I took that deployment folder and used that since I could not use the deployment tool. Worked just fine
i have the same problem with 21.2.4 and vs 2022
Hello guys,
I'm afraid we have not fixed the issue yet. We are working on it. We will update this thread and you will receive the corresponding notifications as soon as we have any news.
Thanks,
Andrey
No solution yet? Visual Studio 2022 is no longer a preview version and still doesn't work.
Hi, got the same problem. Not able to get the necessary DLL's into the project.
We also use the Assembly Deployment tool to find missing DevExpress references. I can confirm that version 21.2.3 of this tool does not work in Visual Studio 2022. It seems to work fine in Visual Studio 2019.
You are right. The issue is specific to VS2022 and we are already working on this problematic behavior. As a temporary solution, it should be possible to use this tool in VS2019.
I will let you know when we have news in this regard.
Thanks,
Andrey
It is also not available on my VS2019
Hello Amador,
The fact that the Assembly Deployment Tool is not working in Visual Studio 2019 on your side makes us think that you encountered a problem that is not related to the version of Visual Studio. I see that you are already discussing this case with my colleagues in the T1044633 private thread. So, would you please update that thread with the diagnostic information and logs that we requested there:
This information will help us to diagnose your particular case. We are looking forward to your reply in the T1044633 private thread.