[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework

.NET 2.0 and .NET 3.5 app not starting after upgrade to .NET 3.5 S

Dierk Droth

8/14/2008 5:36:00 AM

Hi,

We are a vendor of a .NET app which is built using VS2005 and .NET 2.0. This
app used to run fine on any machine where .NET 2.0 runtime or higher is
installed.

After installing .NET 3.5 SP1 runtime this app no longer could be run. Here
are some details:
- double click on desktop icon -> app will not start
- Start->Run -> app will not start
- on my dev XP machine I get it to run in debug mode no problem
- if I try to run it in release mode from VS2005 iI get
System.AccessViolationExceptions: "Attempted to read/write protected memory.
This often is an indication that memory is corrupted."
- this in confirmed on various customer machines running PX or Vista
- exact same problems when trying the latest dev build of our app which is
built using VS2008 and .NET 3.5

This is quite a nightmare and I'm looking for a resultion asap.

Any feedback would be appreciated.

Dierk
1 Answer

Pavel Minaev

8/14/2008 4:55:00 PM

0

On Aug 14, 9:36 am, Dierk Droth <DierkDr...@discussions.microsoft.com>
wrote:
> Hi,
>
> We are a vendor of a .NET app which is built using VS2005 and .NET 2.0. This
> app used to run fine on any machine where .NET 2.0 runtime or higher is
> installed.
>
> After installing .NET 3.5 SP1 runtime this app no longer could be run. Here
> are some details:
> - double click on desktop icon -> app will not start
> - Start->Run -> app will not start
> - on my dev XP machine I get it to run in debug mode no problem
> - if I try to run it in release mode from VS2005 iI get
> System.AccessViolationExceptions: "Attempted to read/write protected memory.
> This often is an indication that memory is corrupted."

Does it happen before the execution of your actual code begins, or is
it a specific line in your code that causes it to happen? If it is the
latter, posting it, and the surrounding related code, would help
pinpointing the issue.