Dynamics GP AddIns are great. You can use Visual Studio and your preferred .NET language to create powerful enhancements for Dynamics GP. And the AddIns are neatly packaged in a DLL file that you simply need to copy into the GP AddIns folder.
But, of course, there are some downsides, one of which is testing and debugging. One issue is that if you need to modify your code, you need to recompile the DLL file, close GP, copy the new DLL file, then re-launch GP. It's tedious and time consuming.
If you aren't accessing any GP windows or Dynamics objects, you can write a wrapper EXE to test your DLL independent of GP, but if you are using Dynamics objects, you need to update your DLL and test in GP. After closing and launching GP a dozen times, you'll be fed up.
Following on my solution for resetting GP when testing with Integration Manager
, I've created a very similar solution for testing GP AddIn DLLs.
I needed the following:
- Close GP
- Copy my new DLL to the AddIns folder
- Launch GP and login again
For this particular project, I'm developing on Windows 2008 with SQL 2008 and GP 10, so I…