Why does dotPeek only show build type (Release/Debug) based on the folder it's in?
If I take an assembly built for debug, and place it in a release folder (for instance on the Desktop, but in a folder named release), opening the assembly from the project original location will show it as being a debug build in dotPeek, but opening the one on the desktop will show it as a release build. This seems like glaringly incorrect way to determine the build type of an assembly.
Please sign in to leave a comment.
Hi John!
For now, dotPeek detects build type by a folder, as this is the quickest method. This allows you to check assemblies with the same names but in different folders, like Debug/Release.
Could you please tell us a bit more about your use case, so we can investigate other options to detect build types?
Thanks!
Well the use case should be pretty obvious, but if all I am given is a .NET assembly to review, and I want to determine if it was built in Debug or Release mode, that information is at best unavailable… and at worst incorrect (say I place a Release assembly under a Debug folder, or vice versa).
There have been instances when an unexperienced developer has mistakenly deployed an assembly built in Debug mode to a production line server, where the rest of the application was built in Release mode (which can and has impacted performance, mostly due to code included by DEBUG preprocessor directives). Identifying the offending DLL and reason for the issue becomes critical. Being able to identify the assembly was built in Debug mode would help to explain these situations and bring to light errors in the development/deployment process.
Hi John!
Thank you for the details!
I've created a feature request, feel free to follow it. We'll investigate if there are any other options. You can see all the progress in the issue.
Should you have any other questions or concerns, please let me know. Have a great week!