We found an interesting article about improving performance of Entity Framework by using "precompiled views": http://neverindoubtnet.blogspot.ch/2012/03/squash-entity-framework-startup-time.html
We have tried this - we use the EF Power Tools extension to auto-generate the precompiled views. Our application was still running afterwards, but I have doubts whether these views are being used at all.
The article above states that SQL Express must be installed. We use DevArt dotConnect with an Oracle database. I wonder how the Microsoft-cooked EF Power Tools should know how the correct SQL for the precompiled views looks like. Does it look at the web.config and find that dotConnect is the provider and retrieve the SQL statements from that provider?
To lead this ad absurdum, I messed up all the strings in the precompiled views file (DataContext.Views.cs) and ran the application - it still worked perfectly.
I have doubts whether these views are being used at all
Set a break point in the context constructor in the file with a precompiled view to find out if the view is used by runtime.
I messed up all the strings in the precompiled views file (DataContext.Views.cs) and ran the application - it still worked perfectly.
EF runtime doesn't use a precompiled view if it was modified manually.
Related
Using the NET Upgrade Assistant, it informed me that it couldn't perform the migration since the code was not in .NET Full Framework. For code to operate in the new NET world, is that a requirement or is that a assistant issue? Can I just create a new project and manually move everything to it?
The error is
[09:22:29 ERR] Support for Web Forms is limited to .NET Full Framework. To learn more please read: aka.ms/migrate-web-forms [09:22:29 ERR] Project C:\Projects\IC\VS2022\SentryServices_NET5_Dev\WWW\www.csproj uses feature(s) that are not supported.
Well, web forms is so old, it's no longer supported in .NET Core or .NET 5.
You can read the link the error message gave you, to find out what you can do about that.
You will have to rewrite considerable parts of your app. While it is possible to just copy over source code files, that only works if the code written would work under .NET 5. If it wouldn't, like web forms, then there is no real migration path other than rewrite it.
Converting Existing Dnn Application to .Net core
I have a application of dnn having ado which I need to convert to .net core with ado web application.
In this I have to move only two modules from the application.
what i have already tried so far.
cleaned the database from the dnn tables.
changed the ascx pages to partial views.
changing the ascx.cs pages to the controller.
Need Recommendations for fast conversion and if I can follow any pattern.
Given the nature of the way that the DNN Platform works, there is not a fast transition to a stand-alone installation.
There is no Microsoft documented "Fast" transition plan from Web-Forms to .NET Core as well, so nothing that you can try to mimic from other installations either.
Since you will need to extract dependencies on DNN as well as dependencies on System.Web that are no longer available, it is best to treat such a transition as a re-write, rather than trying to "simply translate" as there isn't any method to do so.
I am new to ASP.NET Web Forms. Now I am having a small project that I have develop it in ASP.NET. This project consists of the following:
1. data entry system: adding, editing and deleting users
2. defining two roles of the users: admin or registered user
3. creating, editing and deleting events
4. creating simple reports with some graphs
I am expert with HTML, CSS and Javascript. Also, I have a good background in C# and I used Oracle database during my university life, so I know SQL language.
I finished the Lynda Essential Training about ASP.NET and now I am thinking to start my project but I am confused about my start and I don't know from where I should start.
In addition, I have the following questions:
1. Should I know Entity Framework and know how to use it and use it in my project? Is is possible to develop the website with the SqlDataSource?
what is the best and short approach to develop this website from your experience?
Do I need to take another tutorial or is it fine to start with project and taking specific tutorial for each problem that I will face?
Your help guys is highly appreciated
There were a few decisions to make:
Project Type
Web Project or Web Application Project
See http://msdn.microsoft.com/en-us/library/dd547590.aspx
Pattern
MVC or classic Web Forms
See Biggest advantage to using ASP.Net MVC vs web forms
Data Access
Entity Framework (currently in BETA for use with Oracle, see http://www.oracle.com/technetwork/topics/dotnet/downloads/oracleefbeta-302521.html), LINQ to SQL, System.Data.SqlClient classes
I am building a very small temprorary website that needs a small backing store. I have built this in ASP.NET MVC 2, and wanted to host with DiscountASP - although this isn't essential.
I would like an backing store that will work with ASP.NET MVC 2, VS2010 Express, enabled LINQ (or EF) and work without further charges on a shared host.
From my investigation, SQLCE 3.5 doesn't work in .NET 4
SQLCE 4, is only CTP and doesn't work in VS2010
SQlite doesn't have any .NET 4.0 drivers.
HAve I got this right? Any good tutorials or blogs that show how to get this working step by step?
Thanks,
Mark
SQLite does work on .Net 4.0. Here are some other very similar questions about embedded databases in .NET:
Good embedded database solution (like SQLite) for .Net
Embedded database for .net
Open Source Embedded Database Options for .Net Applications
I'm not an ASP expert but have you heard about Firebird SQL? Database engine which has client/server or embeded versions, fully featured with transactions etc. and with ADO.NET provider
http://firebirdsql.org/dotnetfirebird/
http://firebirdsql.org/index.php?op=devel&sub=netprovider
No, Dont even think about using firebird embedded in ASP.NET.
It is strictly forbidden.
here's a reference on Firbird website tell you to avoid:
Is it possible to use the embedded Firebird in my ASP.NET application?
Yes. But Firebird ADO.NET looks for the fbembed.dll file in the application working directory. For ASP.NET application the working directory is the system folder (e.g. C:\WINDOWS\System32). But it's not without problems
link text
On Another page from the same website:
ASP.NET uses a feature that help against poorly written ASP.NET application to block the entire server - it recycles the ASP.NET working process both regularly. By default, IIS6 uses overlapped recycling where there is a new process started before the old is stopped to ensure uninterrupted operation. The problem is that the fbembed.dll exclusively locks the database for the owner process so if you run another process simultaneously the database won't be accessible before the first process stops. You might want to accept this but it really is not an optimal solution.
The solution is to turn off the overlapped recycle (by setting the DisallowOverlappingRotation metabase property to true). However, this might cause outages of your application during recycle.
Conclusion
Don't do tha**t ;-). Really, fbembed.dll **was not built to handle such use. You can make it work but it is just a hack.
I am working on a CMS project using ASP.Net 3.5/Visual studio 2008.This is the first week of the project and I am working on the design of the system right now.
Needless to say that this is my first project of this scale and I have no idea of what I am doing.
The requirements of the project ask for a light but functional CMS, one which is easy to deploy.So the question is which database to use in this scenario SQLCE or SQLite?
I would use SQL Express with the Entity Framework. There are just too many gotchas with SQLCE and SQLite - things that work just fine with SQL Express but which don't work with either one or both of these.
Sure they offer a slightly easier install path but SQL Express is a free download and it's not hard to install.