简体   繁体   English

升级到.Net 4.0后的AccessViolationException

[英]AccessViolationException after upgrade to .Net 4.0

I upgrade a wpf desktop application from .net 3.5 to .net 4.0.(Changed the target framework to 4.0). 我将wpf桌面应用程序从.net 3.5升级到.net 4.0。(将目标框架更改为4.0)。 After the upgrade it shows some unexpected behaviours. 升级后,它显示了一些意外的行为。

There is a tab control in the application. 应用程序中有一个选项卡控件。 when i click a particular tab only either one of the following behaviours occurs. 当我单击特定的选项卡时,只会发生以下任一行为。
1. Application crashed 1.应用程序崩溃
2. AccessViolationException "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." 2. AccessViolationException“试图读取或写入受保护的内存。这通常表明其他内存已损坏。”
3. Application closed 3.申请已关闭
4. Sometimes working fine. 4.有时工作正常。

Other than this tab control issue, application closed unexpectedly. 除了此选项卡控件问题外,应用程序意外关闭。 (when closing a tab or scroll a window). (当关闭标签页或滚动窗口时)。 Sometiems Fatalexecutionengine exception also thrown. 还引发了Fatalexecutionengine异常。

Everything worked fine before converted to .Net 4.0. 在转换为.Net 4.0之前,一切工作正常。

I don't have any clue what's happening there. 我不知道那里发生了什么。 Please help to resolve this. 请帮助解决此问题。

did you try to manually delete all the assemblies then rebuild everything with the new framework ? 您是否尝试过手动删除所有程序集,然后使用新框架重新构建所有程序集? Visual Studio is often like windows, it needs to redo everything lol Visual Studio通常像Windows,需要重做所有内容

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 .NET 4.0 - AccessViolationException和WndProc - .NET 4.0 - AccessViolationException and WndProc 为什么AccessViolationException无法被.NET4.0捕获 - Why AccessViolationException cannot be caught by .NET4.0 升级到VS 2010和.NET 4.0后LINQ停止工作 - LINQ stopped working after upgrade to VS 2010 and .NET 4.0 ApplicationSettingsBase.Upgrade() 使用 .NET 4.0 重新编译后不升级用户设置 - ApplicationSettingsBase.Upgrade() Not Upgrading User Settings after Recompiling with .NET 4.0 .NET Framework升级后(.NET 4.0至.NET 4.5.1)的DLL冲突 - DLL's conflict after .NET framework upgrade (.NET 4.0 to .NET 4.5.1) 在升级到VS 2010 / .NET 4.0后,Membership.ValidateUser始终返回false - Membership.ValidateUser always returns false after upgrade to VS 2010 / .NET 4.0 如何在.Net 4.0中发出异步http POST请求而不遇到AccessViolationException? - How can I make asynchronous http POST requests in .Net 4.0 without encountering AccessViolationException? 如何自动将.Net 3.5升级到.Net 4.0,包括引用? - How to upgrade .Net 3.5 to .Net 4.0 automatically, including references? EnsureDeletedAsync 在升级后损坏,.NET 3.1 到 .NET 6 - EnsureDeletedAsync broken after upgrade, .NET 3.1 to .NET 6 将.net更改为4.0后ValidateRequest停止工作 - ValidateRequest stopped working after changing .net to 4.0
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM