Skip to main content

Notifications

Announcements

Check out the New Agent Creator Community
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / VS 2013 and GP 10
Microsoft Dynamics GP (Archived)

VS 2013 and GP 10

(0) ShareShare
ReportReport
Posted on by Richard Wheeler 75,848 Moderator

We are making progress in getting one of our clients to upgrade to GP 2013 R2.  They are using GP 10 and the first steps was to upgrade their workstations from XP to W7. We have several VS add-ons and in those add-ons was a lookup screen. Since the upgrade of the workstations the lookup screens only work the first time they are called. After that they must be closed and reopened before they will return values.  My first thought was the version of Dot Net so I rebuild them using Dot Net 3.5 but that did not help. So now I am thinking of using VS 2013 as opposed to VS 2008 to build these add-ons.  My question is will the VS Toolkit for GP 10 be compatible with VS 2013?

*This post is locked for comments

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: VS 2013 and GP 10

    Progress is slow sometimes. These folks are an old GPA for DOS client of ours. It took years to get them to Dynamics GP and then years again to get them to W7. My original development machine was Vista and then Windows 2008 R2 server. All was fine until they moved my code to W7 64 bit computers. So I built a new W7 64 bit development image and moved the projects over there and the lookup screens work again. I even tested both your idea and Steve's idea on the old computers I simply did not get any response the second time around so I have nothing to go on for this issue. Thanks for the tip. It was worth a try.

  • John Lowther Profile Picture
    John Lowther 5,122 on at
    RE: VS 2013 and GP 10

    Hey Richard,

    This may not help at all, and it has been a while since I use the VS Tools for GP.

    However, I do use VS for other things, and I have seen this behavior before. Something you could try is to move the code from the form load event into the form activate event.

    Just a thought after a long day at work,

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: VS 2013 and GP 10

    Steve, I added your line but it did not report anything. Oddly enough, I put up a new W7 64 bit image and did a fresh install of GP 10, VS 2010 and VS Tools for GP and now when I build these projects the lookup window works as it should. This was most likely and example of new vs old and new wins!

  • steveendow Profile Picture
    steveendow 2,281 on at
    RE: VS 2013 and GP 10

    Wow, I didn't even notice the lack of a custom install option when I installed VS 2013. Agreed, that is annoying.

    I have used VS 2010 for several years and know that it works fine with GP 2010 and 2013 AddIns, so that should allow you to rule out VS and .NET as the issue.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at
    RE: VS 2013 and GP 10

    Thanks Steve, I will give this a try. Since I just discovered that with VS 2013 you no longer have the option of only installing C#, I decided to use VS 2010 as I do not have unlimited space on this image. What was Microsoft thinking by taking away the option of which language to install?

  • steveendow Profile Picture
    steveendow 2,281 on at
    RE: VS 2013 and GP 10

    Hi Richard,

    I'm skeptical that VS 2013 would help.  I tend to think of VS as just the code editor, with VS 2013 just being able to support the latest version of .NET.  I can't see how the Visual Studio version would be the culprit.

    Are you seeing any errors?

    You might try adding this line of code to see if there might be an unhandled exception occurring.  I recently had an integration that was failing to fire the Form Load event because of a bad reference.  There were no errors at all--but the Form_Load code wasn't being called at all.

    After some digging, I found that this isn't uncommon, and one recommendation was to catch unhandled exceptions.  Sure enough, once I added this one line of code as the first line in my Main() method, I got an error message that pointed me to the problem.

    Application.SetUnhandledExceptionMode(UnhandledExceptionMode.CatchException);


    Try adding that and see if any errors show up.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Check out the New Agent Creator Community

Quick Links

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Last month Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans