Jdpaint Official Website ◉
Drop a comment below about your relief carving workflow.
When visiting, use Google Chrome’s auto-translate feature (unless you read Mandarin). Ensure you are on the genuine domain (usually jingdiao.com or jdpaint.cn )—phishing sites mimicking JDPaint are common on CN tool forums. jdpaint official website
Look for the "VeriSign" or "TrustAsia" SSL certificate. Official Chinese industrial sites invest heavily in HTTPS security. Drop a comment below about your relief carving workflow
JDPaint is a specialized CAD/CAM platform developed by Beijing Jingdiao Technology Co., Ltd. for 2.5D/3D relief design, surface editing, and precision engraving. It supports advanced scanning methods, comprehensive toolpath strategies for machining, and direct, optimized output for Jingdiao CNC machines. For more details, visit JDPaint at software.informer.com . JDSoft ArtForm - Jingdiao Look for the "VeriSign" or "TrustAsia" SSL certificate
Assuming you have a legitimate license or are downloading a viewer, follow this protocol:
: This is the current professional CAD/CAM platform that has largely replaced the legacy JDPaint for 3-axis to 5-axis machining.
I can imagine it took quite a while to figure it out.
I’m looking forward to play with the new .net 5/6 build of NDepend. I guess that also took quite some testing to make sure everything was right.
I understand the reasons to pick .net reactor. The UI is indeed very understandable. There are a few things I don’t like about it but in general it’s a good choice.
Thanks for sharing your experience.
Nice write-up and much appreciated.
Very good article. I was questioning myself a lot about the use of obfuscators and have also tried out some of the mentioned, but at the company we don’t use one in the end…
What I am asking myself is when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
At first glance I cannot dissasemble and reconstruct any code from it.
What do you think, do I still need an obfuscator for this szenario?
> when I publish my .net file to singel file, ready to run with an fixed runtime identifer I’ll get sort of binary code.
Do you mean that you are using .NET Ahead Of Time compilation (AOT)? as explained here:
https://blog.ndepend.com/net-native-aot-explained/
In that case the code is much less decompilable (since there is no more IL Intermediate Language code). But a motivated hacker can still decompile it and see how the code works. However Obfuscator presented here are not concerned with this scenario.
OK. After some thinking and updating my ILSpy to the latest version I found out that ILpy can diassemble and show all sources of an “publish single file” application. (DnSpy can’t by the way…)
So there IS definitifely still the need to obfuscate….
Ok, Btw we compared .NET decompilers available nowadays here: https://blog.ndepend.com/in-the-jungle-of-net-decompilers/