Quantcast
Channel: Microsoft Dynamics CRM
Viewing all articles
Browse latest Browse all 71679

Forum Post: if you have to debug a lot - what approach is best practice ?

$
0
0
Dear all The last few days I did read a lot of debugging of CRM C# plugins. But I still don’t know what isthe best approach is when it comes to “heavy” debugging. Lets’ assume you have to write a new plugin using Visual Studio and you have write a lot of code. Thus a lot of testing, changing code, deploying, testing, changing code, deploying, testing and so on is necessary. What is the most efficient and convenient way when you have to do this? Here my questions. I’m using a developer VM which gives complete isolation from other developers. Obviously I would use Visual Studio to write and debug the code. When it comes to deploying. What is more efficient? So far I’m using CRM toolkit to deploy my changes to the CRM server. I right click on the solution in VS to rebuild and deploy the code. Does this make sense ? Or would it make more sense to use the plugin registration tool? Somehow I don’t like the idea of using it EVERTYTIME I change my code. What I’m not 100% sure about as well: Is it better to deploy the code to the database or to the disk. Somewhere I was reading that if you still have debug a lot it’s better to deploy the plugins to the disk. But why ? What I as well don’t understand is: Under which circumstances do I need to copy the debug file to bin/assembly folder of the CRM server? Only if I deploy the plugin to the database ? And do I need the replace the debug file after each code change ? Otherwise the code changes are not reflected on the server and can’t be debugged? Many thanks for sharing your experience on these aspects! Thanks Alen

Viewing all articles
Browse latest Browse all 71679

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>