Notifications System.IO.FileLoadException

@solamour from a developer’s point of view, logging these conflict messages to a console in Dynamo is just enough. There is no need to flash them at users all the time. Most users never looks at the console, nor do they know that it exists. Developers should be familiar with it.

From a user end point of view, unless there is a critical issue where a package failed to load because there was a conflict, there is no reason to print them up on the ribbon, and keep them up there for every session.

So in summary, keep these messages in the console for developers, only show them on the ribbon if they are CRITICAL and caused actual failures in package loading process, but remove all other warnings.

In regard to development process, a sample Dynamo Revit Package where multiple versions of Revit are supported, and no conflict messages appear at load time, would be awesome. Please post one to GitHub, and I will be happy to implement these changes into archi-lab.net. cc: @john_pierson

4 Likes