Got "exe has stopped working. Close program" in VS 2013 Premium edition after updating from VS 2008

Question

0.00/5 (No votes)

See more:

I have developed VB.Net windows application VS 2008.
Now I am updating that application in VS 2013 Premium edition with .Net framework 4.5.1. After updating suddenly I am getting "exe has stopped working. Close program.". At any time anywhere.
And also while debugging I got System.accessViolation error.
I tried to update framework 4.5.1 to 4.5.2. I also tried to Update target CPU from "Any CPU" to
"X86" as well as "X64". But getting same error.
But after updating framework 4.5.1 to 3.5 it is working fine in VS 2013 Premium edition.
Please suggest me how can I run my program in framework 4.5.1 or onward versions.

Thanks in advanced.

Posted 26-Sep-15 2:02am

nimeshketan

Add a Solution

Comments

Richard MacCutchan 26-Sep-15 9:03am

I tried to update framework 4.5.1 to 4.5.2. I also tried to Update target CPU from "Any CPU" to "X86" as well as "X64".

Why, what indication did you have that this was the issue? If your program stops working then you need first to diagnose the problem. Blindly changing things is more likely to mask the problem than solve it.

As to a solution it is anyone's guess since we have no idea what your code is doing.

nimeshketan 2-Oct-15 2:20am

It is Library Management Application which manage Book/Manuscripts/Magazines. it also manages Publishers/Authors/Readers.

we are using some references of our other applications, and we had converted all those dll's (to same .net framework as Library Management Application ).

We have used MS Office Introp Word 15 DLL to read Word file from our Application.

We have also used Acrobat Browser Control Type Library 1.0 DLL to show PDF in our Application.

Dave Kreskowiak 26-Sep-15 10:34am

Your question is impossible to answer with the information you've given. We have no idea what your application does nor do we know what it was doing at the time of the crash. Without knowing that and seeing the code around the crash site there's no way anyone can answer this question.

nimeshketan 2-Oct-15 2:21am

It is Library Management Application which manage Book/Manuscripts/Magazines. it also manages Publishers/Authors/Readers.

we are using some references of our other applications, and we had converted all those dll's (to same .net framework as Library Management Application ).

We have used MS Office Introp Word 15 DLL to read Word file from our Application.

We have also used Acrobat Browser Control Type Library 1.0 DLL to show PDF in our Application.

Dave Kreskowiak 2-Oct-15 9:37am

OK, so what was the code doing at the time of the crash?

nimeshketan 3-Oct-15 6:28am

it crashes on any action on any form, sometimes it stops on form loading, sometimes on inserting/updating/deleting, while sometimes its working fine.

Dave Kreskowiak 3-Oct-15 10:56am

You're still taking in generalities. That makes it extremely difficult to narrow down the problem. You're going to have to run the debug version of the code on the machine and use the remote debugger to narrow this down.

There is no breaking change like you describe between .NET 3.5 and .NET 4.x.

sreeyush sudhakaran 28-Sep-15 1:17am

Are you using any Memory access APIs , Interop Services or Native Dlls in your Program?

nimeshketan 30-Sep-15 1:49am

yes we are using interop.word dll for microsoft office 15.

sreeyush sudhakaran 4-Oct-15 12:14pm

Try to upgrade to new version of Interops , else your application also will hang

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)