I am new to .Net nuke, I want to display the records in Repeater control and do some group by functionality and order by functionality from database(Sql server 2008 R2) and I need to use( .Net Nuke 6.0 & Entity Frame Work 4 or 5), I have to follow MVP, please give me any suggestions, Thanks
If you are looking to use DotNetNuke for your own purposes, you can use Entity Framework without any special considerations.
If you are looking to deploy a commercial solution on DotNetNuke, you will want to consider the use of the {objectQualifier} and {databaseOwner} configuration options. As supporting those is important for widespread DotNetNuke support and not 100% easy to do with EF.
You should consider using PetaPoco over entity framework. DotNetNuke 7.x has PetaPoco support built in and, IMHO, is a much better solution.
Learn More: http://www.charlesnurse.com/Blog/tabid/226/EntryId/56/DAL-2-Caching-Scoping-and-Custom-Mappings.aspx
Related
What's your opinion?
Should I invest time learning UWP+C# or WPF+C#?
To me they both look very similar, except the fact that UWP was built to run in Windows 10 devices... In the other hand I'm also reading that UWP is not going so well....
The your question is related to Entity Framework. Some time ago I read that EF 7 was going to replace EF 6, now I was searching for EF 7, and appears that EF 7 is still in RC1 and never passed that... Microsoft gave up on that one?
What is the best option (for now and future) to DB access that I could use with WPF or UWP (preference for support with SQL, SQLite, and other formats)?
Certainly in my area, there is far more WPF development than UWP. I think that is likely to be the case for some time because there's way more functionality in WPF.
Entity Framework is very popular and a good choice to learn for commercial employment.
All in all WPF and EF are a good choice if you're talking desktop development.
It has to be said that there are more employment opportunities for web developers nowadays though.
There are probably some cold hard stats could back this up but you just need to look at job ads if in doubt.
Opinion based questions are typically discouraged. Regarding EF Core, it's released (supported by Microsoft) and it's under active development.
I'm looking for some kind of ORM that can be used with Metro Style apps. I found lots of posts referring to different SQLite implementations that seem to be working (or not, according to other posts) with Metro style apps, but no working sample projects so far showing an ORM on Windows 8 Metro. Other posts are referring to projects that might work, but not pass the Marketplace certification because of forbidden API calls.
Lots of the information I found is probably outdated, so I'm not sure if i even googled this right.
Has any of you managed to get some kind of ORM up and running in a Windows Metro style app? If possible, I'd like to use EF Code First, but I'm growing desperate, so I'm not too picky.
Thanks for your suggestions,
Adrian
I'm currently using SQLite on a C# Windows 8 Metro App using the code from an experimental branch as explained by Tim Heuer in this post (there's also a video), and it is working great, and it will pass the store certification (Tim Heuer also mentions it in the post).
It is not Entity Framework, but it is the best we have available so far for working with local databases.
Other alternatives:
IndexedDB (It's an HTML5 feature, so it is only for HTML5 apps)
SQLite - AFAIK it works, but doesn't pass the store certification yet
WinRT File Based Database - Interesting, though not as performant as SQLite
Siaqodb - Interesting. Didn't test it yet
Sterling NoSQL OODB - Doesn't support WinRT just yet, but should not be difficult to port... I expect a release soon. It is NoSQL, though.
As Ladislav says, it is currently not possible. You can, however, use WCF Data Services (OData) on the WinRT platform. For more information, see Phani's post on Developing Windows 8 Metro style applications that consume OData.
As far as I know it is not possible because .NET for Metro doesn't even have System.Data namespace and all required classes for accessing databases.
We're a small software company, developing projects for manufacturing facilities about analysis, traceability, reporting etc. We're using Access for front end, SQL Server for back end. We've quite big customers too and our company is growing. So far it is working fine but I wonder should we move to more influential technologies, such as web based solutions. What do you think about the future of Access?
Well, keep in mind that Access now has a web option. This option works with SharePoint and the new upcoming office 365. Here is a video of an Access application and note how at the half way point I switch to running the application 100% in a web browser. No ActiveX or Silverlight is required. I even tested and run the application on my iPad.
Video here:
http://www.youtube.com/watch?v=AU4mH0jPntI
And Access 2010 also has baked in support for the Azure (cloud) edition of SQL server.
So, we have web based options, cloud based options, and there been significant investments into Access for 2010.
You could have a look at these questions:
MS Access as Enterprise Software?
and
What are the appropriate uses for MS Access?
Here we have a central SQL Server database, with both an MS-Access and a Web client interface. MS-Access is history (we started it 5 years ago) and Web is trendy (less than one year old). I must admit that MS Access is still very very efficient and cheap, once you have resolved some MS access specific problems, to which you might find answers here:
Working with multiple programmers on MS Access
How do you use version control with Access development?
Best way to test a MS Access application?
MS-Access, VBA and error handling
You can always use VB.NET Express. It's free, and Microsoft's licensing should still allow you to sell apps created with it (they did with Express 2005).
UPDATE: Access 2013 has better support for web apps than previous versions, and the apps use SQL Server or SQL Azure under the hood by default. So be sure to thoroughly evaluate the latest version of Access before concluding that you need something else.
A very good alternative to Access with similar features is Lightswitch. Here's a quote from MSDN:
Visual Studio LightSwitch is a development environment designed to simplify and shorten the development of businesses applications and data services. LightSwitch makes it easy to create data-centric business applications that can consume a variety of data sources and create clients that can run on a variety of devices.
While Access now has a web option as #AlbertDKallal mentioned (and which is still worth considering as one option), creating an HTML 5 app is the whole focus of Lightswitch. (Note: the original version of Lightswitch required Silverlight, but the newer versions create HTML5 apps that don't require any plugins.) The app will also be more extensible, since it's a .NET app, and for things that require custom programming you can program in C# or Visual Basic rather than VBA.
I should mention at this point that I haven't actually tried Lightswitch yet (!) - I'm currently evaluating it and these are the features that look attractive to me compared to Access. If anyone reading this in the future is curious about what my experience with it was like, feel free to write a comment to remind me.
For some introductory info, see these links:
Showcase Video
Is Visual Studio LightSwitch the New Access?
(Note that this article is about a the original version of LightSwitch, not the latest version.)
And...for a completely different cloud-based option, check out:
https://www.parasql.com/
we are developing a Silverlight 4.0 (C#, .NET 3.5) application using the MVVM design pattern.
Is it possible to create reports on the client-side with the existing ViewModels or does it have to be done on the server-side? On server-side we only have models and we don't want to copy our business logic to the server. I know ServiceHost is not available in Silverlight and we can't use a WindowsService. Non-free solutions are also welcome.
Thanks in advance
Thomas
It can certainly be done but to what extent you need is slightly up to you. Pete Brown posted an example on creating a simplistic report writer which may suffice based on your needs and is free; allowing you to build on top of the example as needed.
If you moved up to .NET 4 you could leverage the Silverlight Reporting project on codeplex.
telerik also offers a reporting package; however it is not free and requires the full .NET runtime for generation. Don't confuse the .NET runtime as an assumption that it must be server side generation as that is not the case.
I have a project I'm thinking of doing in F#, but I'm still very new to the language. I'll need a simple database, hopefully something easy to use. Would sqlite work well for an F# project? Other suggestions?
SqlLite is a very popular lightweight database engine that supports a .Net binding layer which is accessible from F#. It probably the best option for your scenario.
This CodeProject article details how to use C# to bind to SqlLite and is easily transferable to an F# scenario
http://www.codeproject.com/KB/cs/SQLiteCSharp.aspx
Another option would be SQL Server 2008 Compact Edition. I don't have any experience with it myself, but my understanding is that it is just a dll that can be easily distributed with your project.
The programming API is standard ADO.NET (which can be easily used from F#). It also supports LINQ, so if you wanted, you could also call it with F# LINQ (FLINQ) from CodePlex.
Check out db4o, it's just an object store, so it's pretty simple.
Firebird embedded can be a good choice too
The embedded version is an amazing
variation of the server. It is a fully
featured Firebird server packed in
just a few files. It is very easy to
deploy, since there is no need to
install the server. It is ideal for
CDROM catalogs, demos or standalone
desktop applications.