My Prism 4.1 , Silverlight 5 Application have connectivity with oracle 11g via DevArt Oracle connector. My controls will be of Telerik
I've used EnitityFramwork 6 Database 1st Approach. Entitites & Context are in 1 c# project under Data module.
I'm unable to create (OpenRIA)RIA Domain Service library in my Prism project. It doesn't allow me to choose entitites from wizard. Means it doesn't show me the Entitites in wizard.
ITS OPENRIA with VS2013.
RIA Services Domain Services no longer exists as a wizard within Vs2013:
http://msmvps.com/blogs/deborahk/archive/2013/10/25/who-moved-my-cheese-ria-services.aspx
You instead have access to some NuGet packages, and the Open RIA Services project
Related
I am aware of this thread .NET 6 how to add webservice reference but I am creating a VB.NET desktop app and when I go to Connected Services, I don't have the option of selecting Service References as in C#. Only Service Dependencies. Is there a workaround?
I am going to deploy my application tomorrow ,so i have few questions.I want to deploy asp.net mvc4 application on 2003 server where .net framework 4.0 is installed.My question is do i need to install asp.net mvc4 also there.Or if i copy the dll responsible for mvc in to that system is sufficient?
another question is i am using entityframework and oracle database so using ODP.NET, if this is the case do i need to install ODP.NET over there or just copying DLL system.dataaccess dll is sufficient?
Rest all i follow this two links will it work
The two links are http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx/
How to deploy MVC application in 2003 server IIS
UPDATE
today i tried and unfortunately i came to know that the framework which i was running .net 4.5 will not be supported in 2003.I made my project in to .net 4.0 and everything working fine in local system,but remote system lot of errors are coming.Method not found etc. I came to know that i have to degrade EF 5.0 to 4.4 i did it like replaced dll and changed one line begin with section but no luck as of now.I have to change somewhere else also.Do you know any proper mechanism which i need to carry forward for this?
No need to install anything explicitly except .Net 4.0. All you need is make sure that all dependencies (assemblies) of your application i.e. MVC, ODP.Net etc are present in bin directory of your application. Also make sure that ASP.Net v4.0 Web service extension is enabled in IIS.
Steps to enable web service extension.
Open IIS 6.0 Manager
Click Web Service Extensions
Enable ASP.NET 4.0
Check below screenshot.
Quick question
I am doing a Plural Sight tutorial on WCF and they are using the WCF Service Library (as opposed to application.)
When I go to Add new project there is no WCF Service Library. Not under any of the .NET versions.
I am using Visual Studio 2013 for Web Express.
Any one know how I can get it?
Thanks
You can find it under Templates WCF.
( Go to New Project->Installed-->Templates-->WCF)
This is my setup:
MVC app
A domain model with a data access layer using Enitity Framework Code First
Silverlight application (displayed in the MVC App)
I'm using RIA Service to make the Silverlight App interact with the DB.
Ria services only supports entity framework 4.1 as of now. Current release is 4.3. Seems to be a waste to not get the new features of EF (like migrations and hopefully enum support in the future) just becouse of the Ria service for the Silverlight app.
My question is therefore:
Is it reasonable to rely on the Ria Service when using EF code first (i.e. will they always lag behind by so much? Could this be a problem down the road?)
Do you have an alternative solution where the Silverlight app is not so dependent on what version of the ORM i use?
RIA Services can be used with NHibernate or any other ORM or object/domain model. Only some of the VS Wizards imply there is coupling between EF and RIA Services, but you clearly aren't required to use those wizards nor is there a coupling between EF and RIA Services.
The answer to the question "Can I use RIA Services with Entity Framework 4.3?" is absolutely yes.
OData is an alternative to RIA Services, but it has quite a few limitations and is not intended as a direct competitor. WCF is also an alternative.
A workaround for getting migrations before RIA services properly supports EF4.3 could also be to create a project solely for migrations, similar in spirit to the database projects in Visual Studio Ultimate.
The model would need to be included by such a project via "add as link" and you'd need to make sure that it can compile in both projects. For example, you might need to define some dummy attribute that are defined in RIA-Services ("Include" would be one).
It's not ideal but maybe it's the best option in some cases.
To get a temporary workaround for the lock of version < 4.2 of the RiaServices.EntityFramework NuGet package, I've used the NuGet Package Explorer in order to change the metadata of the package and removed the constraint.
Remeber you must add the local cache as NuGet source.
Tools -> Options -> Package Manager -> Package Sources -> Add (C:/Users/%username%/Appdata/Local/Nuget/Cache)
My situation is that I developed a .NET 4 based MVC2 web app, and now I have to deploy it on a Windows Server 2003 that has standalone SharePoint 2007 living on it. My quick research shows that SharePoint 2007 doesn't play with .NET 4. So my questions are:
1) Will SharePoint 2007 break if I install .NET 4 on the server? As far as I know .NET versions were backwards compatible...
2) Is it possible to deploy the .NET 4 assemblies with my web app without actually installing the framework and registering it.
3) Any other tips and advises on resolving this situation?
SharePoint wont'break if you apply latest service packs + cumulative updates to it.
At least I have such a combination running on my servers right now.
It would be a problem, if you tried installing .Net4.0 on the same machine prior to "Infrastructure update" of 2009 (or maybe before SP2?), since, as it was said "SharePoint stored some references to .net4 classes in the configuration database", whatever that means.