Autodesk.Internal.Windows.HideableDialogSettingsDictionary
Thanks for pointing us in this direction.
Loading the Acad release dependent AcTaskDialogs.dll resources seems to be not that difficult and can be done without ILSpy.
[CommandMethod("TestLoadAndStoreTaskDialogResources")]
public static void LoadAndStoreTaskDialogResources()
{
Document doc = null;
Editor ed = null;
Database db = null;
var acTaskDialogsFilename = "AcTaskDialogs.dll";
var outPath = Path.GetTempPath(); //Store output XAML Textfiles
try
{
doc = AcadApp.DocumentManager.MdiActiveDocument;
ed = doc.Editor;
db = doc.Database;
var acadArgs = Environment.GetCommandLineArgs(); //C:\program..\acad.exe /product [product code]
var acadExePathname = acadArgs[0]; //C:\Program Files\Autodesk\AutoCAD 2021\acad.exe
var acadExePath = Path.GetDirectoryName(acadExePathname); //C:\Program Files\Autodesk\AutoCAD 2021
var acTaskDialogsPathname = Path.Combine(acadExePath, acTaskDialogsFilename);
ed.WriteMessage($"Loading resources from: {acTaskDialogsPathname}\n");
var acTaskDialogAssy = Assembly.LoadFile(acTaskDialogsPathname);
using (var acTaskDialogStrm = acTaskDialogAssy.GetManifestResourceStream(acTaskDialogAssy.GetName().Name + ".g.resources"))
{
using (var acTaskDialogResRdr = new ResourceReader(acTaskDialogStrm))
{
foreach (DictionaryEntry acTaskRes in acTaskDialogResRdr)
{
var resFilename = acTaskRes.Key.ToString();
ed.WriteMessage($"\t Extract: {resFilename}\n");
//Let's try all resources, not only hideabletaskdialogs.baml
if (resFilename.EndsWith(".BAML", StringComparison.OrdinalIgnoreCase))
{
var acTaskXamlSb = new StringBuilder();
XmlWriterSettings xmlWrSet = new XmlWriterSettings
{
Indent = true,
OmitXmlDeclaration = false
};
var xmlWr = XmlWriter.Create(acTaskXamlSb, xmlWrSet);
var xmlSerMan = new XamlDesignerSerializationManager(xmlWr);
using (var acTaskBml = new Baml2006Reader((Stream)acTaskRes.Value))
{
try //catches: Source property has already been set on ResourceDictionary
{
using (var acTaskXaml = new XamlObjectWriter(acTaskBml.SchemaContext))
{
while (acTaskBml.Read())
{
acTaskXaml.WriteNode(acTaskBml);
}
ed.WriteMessage($"\t Convert to XAML, waiting....\n");
System.Windows.Markup.XamlWriter.Save(acTaskXaml.Result, xmlSerMan);
var xamlStr = acTaskXamlSb.ToString();
var xamlFilename = Path.ChangeExtension(resFilename, ".xaml");
var xamlPathname = Path.Combine(outPath, xamlFilename);
File.WriteAllText(xamlPathname, xamlStr);
ed.WriteMessage($"\t Save: {xamlFilename}@{outPath}\n");
}
}
catch (System.Exception ex)
{
ed.WriteMessage($"\t Error: {ex.Message}\n");
}
}
}
}
}
}
}
catch (System.Exception ex)
{
ed.WriteMessage(ex.Message);
}
}
And for the other AutoCAD Vertical (Map) users, another resource DLL to look into among others is
Thank you so much. Together, we will go further. I’m still not finished with this project so I may come back later for more informations/comments.
I mentioned ILSpy to make a story short. I did almost as you’ve done but I was uncertain about the consequences of bypassing AutoCAD loading one of its dll and also what would append if you execute the routine twice (this mean trying to reload the dll). You can add a Static flag to avoid this. So, I created a domain in which I loaded the file and I release the domain when it’s done.
' Assuming acTaskDialogsPathname can be the same as yours, namely
' C:\Program Files\Autodesk\AutoCAD 2021\AcTaskDialogs.dll
Dim path As String = Application.StartupPath
Dim setup As AppDomainSetup = AppDomain.CurrentDomain.SetupInformation
setup.PrivateBinPath = Path
setup.ShadowCopyFiles = "false"
Dim NomDomaine As String = "MyDomain"
Dim domain As AppDomain = AppDomain.CreateDomain(NomDomaine, Nothing, setup)
Dim assy As Assembly = Assembly.LoadFile(acTaskDialogsPathname)
. . .
AppDomain.Unload(domain)
I thought I had harvested all the cases for a vanilla AutoCAD but no. I Drag&Drop some of my problematic drawings and got at least 5 cases that came from nowhere. So, it’s gonna be a long and winding road. The caption in the following excerpt are in French but with the ID, you can deduct the meaning without translating.
<HideableDialog
id="Acad.UnresolvedFontFiles"
title="Fichiers SHX manquants"
. . .
</HideableDialog>
<HideableDialog
id="Acad.UnresolvedReferenceFiles"
title="Références - Fichiers introuvables""
. . .
</HideableDialog>
<HideableDialog
id="AecUiBase.PreviousVersionOpen"
title="Ouvrir le dessin - Objets AEC d'une version antérieure"""
. . .
</HideableDialog>
<HideableDialog
id="AecUiBase.SavingToPreviousVersion"
title="Enregistrement du dessin - Conflit de versions"
. . .
</HideableDialog>
<HideableDialog
id="DWGRecovery.DrawingRecovery"
title="Récupération du dessin"
. . .
</HideableDialog>
My approach now is the following. A dialog box (a different one of course) helps the user to choose which the dialog to hide or unhide. A TreeView has 2 nodes.
- The first one to encapsulate the AcTaskDialogs nodes having a mandatory attribute AllowDialogCancellation="True".
- The second node encapsulates the other cases (the exceptions). I have a second exe file that has a System.IO.FileSystemWatcher to spy the modifications in the FixedProfile.aws file. The latter is only updated when AutoCAD closes. Doing so, I can build a satellite file or an equivalent of a App.Config file for the exceptions. I use the PostBuildEvent to copy back this satellite file in the dll directory.
First node:
Second node:
Some of the BAML nodes do not have the attribute AllowDialogCancellation="True". This Print Screen is a clear case (this may be not the exact translation: “The sheet set association is lost. What do you want to do?”). You can’t avoid this dialog if you face the problem. That’s why they are not listed in the first node.
Nice cooperation!
I was wondering what more resource (dll) files may be of interest. Extending the code a bit made me harvesting all the files, see attachment for the complete.
Also improved the Embedded Resource handling(*.BAMP, *.GIF, *.TIF)
...
var bamlFileName = "HideableTaskDialogs";
...
var dllPathnames = Directory.GetFiles(acadExePath, "*.dll", SearchOption.AllDirectories);
...
var acDllAssy = Assembly.LoadFile(dllPathname);
var acResourceNames = acDllAssy.GetManifestResourceNames();
if (acResourceNames != null)
{
ed.WriteMessage($"Evaluate resources from: [{nDll}]: {dllPathname}\n");
foreach (var acResourceName in acResourceNames)
{
var acResourceInfo = acDllAssy.GetManifestResourceInfo(acResourceName);
ed.WriteMessage($"\t Processing resource: {acResourceName}\n");
using (var acResourceStrm = acDllAssy.GetManifestResourceStream(acResourceName)) // acResourceAssy.GetName().Name + ".g.resources"))
{
using (var acResRdr = new ResourceReader(acResourceStrm))
{
foreach (DictionaryEntry acRes in acResRdr) //*.BAML, *.Gif, *.Tif ...
{
var acResFilename = acRes.Key.ToString();
//if (acResFilename.EndsWith(".BAML", StringComparison.OrdinalIgnoreCase))
if (acResFilename.StartsWith(bamlFileName, StringComparison.OrdinalIgnoreCase))
...
It's processing 2025! dll's in my AutoCAD Map 2019 (including RasterDesign), but only 5 seems to contain HideableTaskDialogs.
This code is far from finished but there seems to be a problem in the .NET framework (...XML parsing...)when multiple runs have executed.
