I am starting on a new large project and I'd like to use EF4 for the data layer stuff, mainly for the POCO mappings feature.
Am I a fool for stating work against a CTP release? Should I wait for the RTM? Given my project will likley take 12 months, could the RTM be out by the end of my project?
I'm sure others have been in the same situation as myself, what did you do and how did you come to that conclusion? I believe that given its CTP 4, the framework shouldn't change all that much, just bug fixes and any new features meaning a the code already laid should remain good.
I'd much rather use this than nHibernate or Linq as it appears (for what I want) to be ideal.
I am in a similar situation with a project planned for release in about 6 months. I am therefore fully behind EF4 CTP and thoroughly recomend using it. There are a few shortcomings at present so there may well be a few changes between now and release, but I am prepared to take the hit on those to get the new functionality early.
Related
There is already 7th beta version of ASP.NET 5, in which they say localization features are done. How can I use localization to write multi-language applications in asp.net 5 mvc 6 with visual studio 2015? Is there any working example project for beta 7 version? I have already searched and found many examples but they no more work because the code has been changed since that. Can I still use .resx files (because visual studio does not auto-generate Designer.cs files any more) or are there any newer or alternative methods they suggest?
Beta 7 introduced the localization, so it's really brand new. I wrote a short write up of everything that is new on my blog. There are a lot of things new, so if you need the features, I recommend reading it.
You can in fact still use Resx, but you have to understand that the resolution by default is, that the engine tries to find the resx file that matches the view.
For example, if you have a HomeController, and an action called Locpage, you need to have Views.Home.Locpage.cshtml.en-GB.resx to Support en-GB locale. The best part, however, is that you don't really need a resx file anymore :-). You can just implement your own implementation of IStringLocalizer and IStringLocalizerFactory, and it'll work. You can see the code for this on my blog, above.
If you want a working sample, the best place right now is their GitHub, so this right here: https://github.com/aspnet/Mvc/tree/dev/samples/LocalizationSample.Web.
I have refereed old questions and found that people face many issues after installing mvc3 and MVC4 on same machine.
My question is how is your recent experience for the same and how the mixture works for you guys.
I want to create one solution which will have four projects out of them two are MVC projects. One is MVC3 and another is MVC4.
Let me know your views on this.
Thanks,
Jigar
In short - there shouldn't be a problem. Once 3 & 4 are both installed, the two use different project templates and the references to the MVC assemblies are specifically targetted at the correct versions.
Beyond that, the web.configs of the two sites then determine the other assemblies that are used - and since they are seeded by the project templates they will be correct.
Now, if you were asking about having 3 & 4 in the same project, that would be another story. But then you wouldn't do that.
It's true there are a few known issues with the Razor editor and stuff like that - but none of those are show-stoppers and are almost certainly likely to have been fixed by the time v4 RTMs.
I've always used VS for .NET development, but am just wondering about the alternatives around now. I'm especially interested in use for ASP.NET MVC development. I'm not bothered about any of the visual design aspects of vs, but of course love intellisense and the debugging features.
So, for anyone who has tried SharpDevelop when doing ASP.NET MVC:
How did you get on?
What are the main disadvantages and pain points?
Thanks
By the looks of it, SharpDevelop won't have any problems compiling the project and editing the source...you just won't get any tooling support. From what I've read, that includes aspx files.
Having said that, there does seem to be some movement around an ASP.NET plug-in editor for SharpDevelop here.
Source: http://community.sharpdevelop.net/forums/t/7872.aspx
As an aside, it might to nice to update this question with your experiences if you go down that route... (:
I have used SharpDevelop to create an ASP.Net WebForms project - didn't have too many issues with it. The lack of a visual designer is certainly annoying, but it forces you to think about the source directly, which is a good thing...
I haven't done anything with MVC yet - though from the sounds of things the only thing that's stopping SD at the moment is the tooling. The core developers might have no plans for that, but it's an open source project, so there's nothing stopping an independent effort.
I've gone a very limited amount of work (bug investigation) with the SD code - it seems to me that once you understand their classes it's not bad code... Their failing as a project has been (as it is with most open source efforts) that everyone wants to code, so the documentation gets ignored. No-one likes writing documentation, but clear documentation might have led to far greater participation...
It's a great project, but their decision to ignore the web is madness.
As Kieron said, you'll be able to compile and you'll lack tooling. Unfortunately, #Develop's forum says that they don't plan to directly support it:
ASP.NET support is not planned for SharpDevelop.
The lack of tooling and knowing that it's not coming anytime soon would be the major pain point for me.
Should I just be able to install the beta on top of this without problems when it is released ?
Not sure how it is treated within the visual studio environment. I'm thinking with it being a type of project in VS it should be ok.
Can anyone clarify?
MVC 2 is looking to be rather good from what I heard from Scott Gu # the Manchester conference, can't wait for the final release :)
There is always a chance of a breaking change when using preview and beta software. If you want to use MVC 2 Preview, you need to accept the fact that there might be some work in your future to make your project compatable with the Beta, RC, and then Final releases. It won't necessarily break, but the earlier in the release schedule (such as a preview instead of a beta) the greater the chances are you'll have to make changes to your code as they move forward.
When MVC 1.0 previews were released, there were breaking changes between the releases. If you try to keep up with each preview, you should be able to resolve any problems rather quickly - and you could provide great feedback, too!
I'd like to create an application using ASP.NET MVC, that should run under mono 2.4 (compiling will be done on a Windows box). Has anyone getting luck with this? Here is what I've already tried:
ASP.NET MVC on mono without any persistence model support, and using nhaml as the view engine
S#aml architecture, which is a quite good framework imho, but it depends too much on stuff, that are not working good under mono (like windsor)
The first part worked fine, I didn't encounter any major problems. But I couldn't get the second part working. It seems it's dependency on Castle.Windsor breaks the whole mono support (but there might be other parts too).
Therefore I decided to create an alternative framework, that borrows some of the ideas of s#arp-architecture, but designed to be working under mono (and if I'm able to do this I'll release it for the community of course). The controller and view part is working fine (not much magic here though, they have been always working), but I have some questions before I start job on the persistence part:
What NHibernate versions are working under mono? I've heard 1.2 is working fine. Does 2.0.1/2.1 beta work under mono?
Does Fluent.NHibernate and NHibernate.Linq work under mono? (for the latter it seems it needs some dependcies that aren't avaialable in mono)
Are there any good alternatives for persistence support to NHibernate under mono?
Alternative questions:
Are there any frameworks that have mono+persistence+asp.net mvc support already or am I the first one to think about this?
If you have already done this: what are your opinions on stability/usability?
Thanks for the answers
EDIT: Updated the framework to support ASP.NET MVC 2: http://shaml.sztupy.hu/
I am using mono 2.4 to run a asp.net mvc app + windows service.
Compatibility is very good. There are some bugs and differences than with windows but once you learn what they are it gets easier (there can be pain at the start!)
I am using NHibernate (2.1) FluentNhibernate, StructureMap, NBehave, Moq and open id lib and they all just seem to work as expected.
As for stability, since I have ironed out the major bugs in my code I haven't had any problems.
Usability, well it is a completely different platform so you need to come to it with an open mind and be prepared to leave behind the windows way.. the good news is that once you do that things get easier. Apache is a lot nicer than IIS and configuring and managing a linux box is just easier than windows.
I am pretty glad I choose mono.. sorry this is starting to sound like a PR drive - but I am just really happy with it!!
Okay. I started on a new project that incorporates the best from S#arp Architecture with stuff, that work on mono. Instead of T4Toolkit it uses a ruby script to do the generation job, just as with rails or merb.
To use install the shaml gem from github:
gem install shaml
Then create a new application:
shaml generate app AppName
And create resources:
shaml generate resource NewRes "name:string;date:DateTime"
S#aml Architecture project homepage: http://shaml.sztupy.hu/
GitHub project: http://github.com/sztupy/shaml/tree/master