Contents tagged with ASP.NET
-
Fix: Add an Existing Entity Framework .edmx File to Visual Studio 2013
One of my older code samples for RainWorx AuctionWorx uses Entity Framework and SQLCE to bulk import AdventureWorks products as sample auction, classified, and fixed price listings into the system.
-
BOGUS Error: JIT Compiler encountered an internal limitation.
Out of the blue, Visual Studio 2013 (Update 2) refused to debug ASP.NET 3.5 Web site projects. The error message was:
-
Fix: Azure Disabled over 49 cents? Beware of using a Java Virtual Machine on Microsoft Azure
I love my MSDN Azure account. I can spin up a demo/dev app or VM in seconds. In fact, it is so easy to create a virtual machine that Azure shut down my whole account!
-
Fix: The type 'System.Web.Mvc.ViewPage' is ambiguous:
Once again, my lack of attention leads to a blog post.
-
EntityDataSource control for Entity Framework 6 Preview
It took a while but we now have a preview version of the EntityDataSource control for Entity Framework 6.
-
Explained: EF 6 and “Could not determine storage version; a valid storage connection or a version hint is required.”
I have a legacy ASP.NET 3.5 web site that I’ve upgraded to a .NET 4 web application. At the same time, I upgraded to Entity Framework 6.
-
Creating a SQL Azure Database Should be Easier
Every time I try to create a database + tables + data for Windows Azure SQL I get errors. One of them is 'Filegroup reference and partitioning scheme' is not supported in this version of SQL Server.'
-
Assemblies Go Missing in MVC 2 Project!
Sometimes, my MVC 2 project fails during development because an assembly has disappeared from the /bin folder.
-
Deleting a Project From TFS.visualstudio.com
I really appreciate having the online Team Foundation Service (http://tfs.visualstudio.com/) as free source control for my personal projects. It has saved my bacon more than once when I’ve needed to roll back my code to a known good point, regroup, and dive in afresh.
-
Fix: The type 'System.Data.Objects.ObjectContext' is defined in an assembly that is not referenced.
I got this message in a class that inherits from DbContext. It made no sense, because System.Data.Entity was definitely referenced in my ASP.NET project.