问题描述
看起来我已经设法创造了完美的风暴。我有一个应用程序已经使用点击一次部署了4年。它是在VS2010上开发的，使用的是SQLCE数据库。当我最近更新我的代码签名证书时，我被迫从SHA1将
升级为SHA256。所以现在当我使用VS2010部署更新时会发生什么，更新失败导致程序崩溃并使其无法运行，因为.net 4.0无法处理SHA256。如果用户在其计算机上安装了.net 4.5或更高版本，则更新
正常工作。但等待它变得更好。我认为一个简单的解决方案是使用更新版本的VS并使用.net 4.6.1重新部署，所以我下载了VS2015社区。 VS2015不赞成对SQLCE的支持，因此不起作用。我发现支持SQLCE的VS的最后一个
版本是VS2012。 要运行VS2012需要MSDN订阅，这对像我这样的兼职开发者来说是一个荒谬的成本。所以现在我被VS2010困住了，我支付了1000美元，有一堆PO用户有一个崩溃的程序
而无法修复它。
任何人都有建议解决我的问题？
Looks like I have managed to create the perfect storm. I have an app which has been deployed using click once for 4 years. It was developed on VS2010 and uses a SQLCE database. When I recently renewed my code signing certificate I was forced to upgrade to SHA256 from SHA1. So now what happens when I deploy an update using VS2010 the update fails crashing the program and making it inoperative because .net 4.0 can't deal with SHA256. If the user has .net 4.5 or better installed on their machine the update works fine. But wait it gets better. I thought a simple solution would be to use a newer version of VS and just re-deploy using .net 4.6.1 so I downloaded VS2015 Community. VS2015 deprecated support for SQLCE so that won't work. I discovered the last version of VS that supports SQLCE is VS2012. To run VS2012 requires a MSDN subscription which is a ridiculous cost for a part time developer like me. So now I am stuck with VS2010 which I paid $1000, have a bunch of PO users with a crashed program and no way to fix it.
Anyone have a suggestion to resolve my problem?
这篇关于.net 4.0，SHA256，SQLCE和VS2010的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！