What is the best version of VB.NET to use for developing EPDM API addins and standalone apps?
What about the free Express versions... are there problems with using them?
I only use VS 2012 for EPDM 2013 because it finally supports .Net4.0. I tried following the guidelines about interops etc for previous versions of EPDM, but for anything pre-2013 I just use VS 2008 because it works by just making the app COM visible.
2008 - 2012 all use VB.Net 2.0, and 2005 will use VB6 and could also use .Net 2.0, but I can't find much documentation from then. I use the free express VS, the only thing I really miss is the ability to debug add-ins you get with the paid version.
Yeah, I noticed that debugging is not included in the Express version. That's probably a deal killer right there...
If you write standalone apps, Express will be okay, but if you are planning on creating add-ins, I wouldn't even consider Express.
Please share your reasons Jeff. I'm interested.
Charley Saint wrote: Brian, 2008 - 2012 all use VB.Net 2.0, and 2005 will use VB6 and could also use .Net 2.0, but I can't find much documentation from then. I use the free express VS, the only thing I really miss is the ability to debug add-ins you get with the paid version.
Charley Saint wrote:
I thought with the Free Express you couldn't create .dll and then couldn't load it into ePDM. Am I missing something?
I use vb.net 2010 express (free) version and it creates .dll add-ins that load into EPDM no problem
The only gotcha to continually monitor are mixed interops installed at the same time. This is nearly a full-time job to ensure if your company has multiple vendors creating add-ins, be careful to understand the interop versions they are written against.
Hope this helps.
Stay away from VS 2012 Express. There is a feature missing you'll wish you had. See this thread.
I also remember there being a limitation that one can not have more than one project per solution. That would be a deal breaker for me.
I decided to go with VS 2008 at this time. With the full version I have addin debugging and I will stick with .COM visibility as Charley suggests since we're currently using SW/EPDM 2012.
Thanks to all who contributed to this discussion and my education.
Retrieving data ...