.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Deploying MVC 2 Web App using EF

Posted By:      Posted Date: September 21, 2010    Points: 0   Category :ASP.Net

Used Visual Studio 2008 to publish web app to a local IIS7 Website but still hooked to VS development .mdf file with EF. With this I can successfully access web app via local host. As long as the development db server is running, web access is fine.

Then I tried to change connection to local .\SQLEXPRESS where I have other databases (this is my production server). I have replicated the development data into the SQLExpress database already.  The connection string appears OK.

The problem is the application's entity data model (.edmx file) is still tied to the development .mdf file.

When I tried to rebuild the entity data model, I can see the production instance in list of db connections but cannot select it. Only the development db objects are available.

So I don't think the problem is related to connecting to the production db. It is more about getting the .edmx file to point to the production table. Either it should migrate over or it needs to be rebuilt. I don't see any MVC deployment help pages discussing EF deployments.

View Complete Post

More Related Resource Links

deploying to msdeploy does not support a proxy server


I am trying to deploy through webmatrix but my system Proxy server configuration is not being used. I assume that webmatrix would detect the proxy server settings and use that for the msdeploy calls under the hood. Can anyone confirm this is a know issue? 

Windows Azure: Developing and Deploying Cloud Apps in Visual Studio 2010


You'll find direct support for building Windows Azure applications in Visual Studio 2010 and Visual Web Developer 2010 Express. We'll walk you through using Visual Studio 2010 for the entirety of the Windows Azure application development lifecycle.

Jim Nakashima

MSDN Magazine April 2010

Cloud Patterns: Designing and Deploying Services for Windows Azure


To better understand how SOA patterns can be applied to Windows Azure deployments, we walk you through a scenario in which a bank moves its services to the cloud.

Thomas Erl, Arman Kurtagic, Herbjörn Wilhelmsen

MSDN Magazine January 2010

SharePoint's Sandbox: Developing, Deploying and Monitoring Sandboxed Solutions in SharePoint 2010


The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.

Paul Stubbs

MSDN Magazine November 2009

Code Name Longhorn: A First Look at Writing and Deploying Apps in the Next Generation of Windows


The next version of the Microsoft Windows operating system, code-named "Longhorn," marks a significant change not only in terms of how the operating system works, but also in the way in which applications are built. The Longhorn version of Windows includes a new storage system, natural search technology, and an increased emphasis on security and trustworthy computing. Here the author provides an overview of Longhorn, focusing on the build-once, deploy n-times application model. In addition, he discusses the new language, code-named "XAML," that's used to create UI elements, then presents some working samples.

Dino Esposito

MSDN Magazine January 2004

The ASP Column: Deploying an ASP.NET App Using Visual Studio .NET


When Visual Studio® . NET was released back in February 2002, it included a number of new features that made it easier to create Web applications. The Microsoft® . NET Framework includes classes for intercepting and processing HTTP requests, and Visual Studio .

George Shepherd

MSDN Magazine November 2002

ASP.NET Security: An Introductory Guide to Building and Deploying More Secure Sites with ASP.NET and


Forms authentication is one of the most compelling and useful new features of ASP.NET. It enables developers to declaratively specify which files on their site can be accessed and by whom, and allows identification of a login page. When an unauthenticated user attempts to retrieve a page protected by forms authentication, ASP.NET automatically redirects them to the login page and asks them to identify themselves. Included here is an overview of forms authentication and what you need to know to put it to work. Also included is hard-to-find information on the security of cookie authentication and on combining forms authentication with role-based URL authorizations.

Jeff Prosise

MSDN Magazine May 2002

ASP.NET Security: An Introductory Guide to Building and Deploying More Secure Sites with ASP.NET and


ASP.NET and Microsoft Internet Information Services (IIS) work together to make building secure Web sites a breeze. But to do it right, you have to know how the two interrelate and what options they provide for securing access to a Web site's resources. This article, the first in a two-part series, explains the ABCs of Web security as seen through the eyes of ASP.NET and includes a hands-on tutorial demonstrating Windows authentication and ACL authorizations. A range of security measures and authentication methods are discussed, including basic authentication, digest authentication, and role-based security.

Jeff Prosise

MSDN Magazine April 2002

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types-Part 2


Part 1 of this series discussed how types built for the common language runtime can be shared among applications in the Microsoft .NET Framework regardless of the .NET languages used to build them. This second part continues with building assemblies by first covering security, sharing assemblies, versioning, localization, and side-by-side execution. Because in .NET two DLLs with the same name can be loaded as long as another attribute-which can include the localization language-differs, versioning is much easier than it used to be, so DLL Hell may become a thing of the past.

Jeffrey Richter

MSDN Magazine March 2001

.NET Framework: Building, Packaging, Deploying, and Administering Applications and Types


Types that are built for the Common Language Runtime can be shared among applications in the Microsoft .NET Framework no matter which of the .NET languages they were built in, an obvious benefit to developers. This article describes the building, packaging, and deploying of applications and types for the .NET Framework, including the role and significance of assemblies, private and otherwise. The way metadata and assemblies help to solve some historical problems like versioning conflicts and DLL Hell, and how they improve system stability are also discussed.

Jeffrey Richter

MSDN Magazine February 2001

Deploying Web Part - Available on features and activated but not available on Web Parts

I have deployed a Web Part using the sharepoint extensions solution deploy of visual studio 2008. It deploys successfully and displays on features where I can go and activate. But them it is not available on webparts and neither available to be added when editing a sharepoint page. Am I missing something? I tried iisreset but still can't see anything

Deploying custom Web Parts on SharePoint 2007 production server

I would like to develop a custom SharePoint 2007 Web Part for a client. Currently I'm using Visual Studio to deploy my solution to a test environment (since it's a SharePoint Project I choose just Build -> Deploy from the menu). What are the appropriate steps to deploy it to the production server?

I'd like keep it simple and safe (i.e. use the principle of least privilege). Therefore (if possible) avoid using stsadm, achieve this through web interface, or avoid using administrative rights.

Also, can I specify the scope of my Web Part, i.e. choose on which Web Application or Site Collection will it be installed?

Deploying InfoPath 2007 form to WSS 3.0 as browser enabled


Please Help! I've created an Infopath form and wanted to deploy the form as browser enabled to WSS 3.0? What are the different options I can do this? If i cannot use a form then i would like to  create a custom list with all the form fields but the user should be able to enter information in the list and he should see only the information related to him. I don't want to give access of the whole list to each and every user. Only the administrator should be able to see the whole list. The form was actually a user access request form.

Any help and suggestions is appreciated.


Video: Deploying Microsoft Office 2010 Applications

Video: Deploying Microsoft Office 2010 Applications Deploying Office Add-ins and SharePoint applications is the topic of this video. It touches on the issues that can slow adoption and the characteristics needed for enabling good deployment scenarios. It also provides an overview of SharePoint Solution (WSP) file and ClickOnce deployments. (Length: 6:14)

OLE DB Error: Network-Related or Instance-Specific while Deploying SSAS 2008 Cube

Hi, I encountered the below listed error while attempting to deploy SSAS 2008 DB: Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [5]. ; 08001.  0 0  I am running a standalone MSSQL 2008 named instance on Windows Server 2008 R2. Here are the steps I have taken but yet the issue is not resolve: 1) Enable Remote connections on the server 2) Enable TCP\IP 3) SQL Browser is Running 4) Set Firewall Inbound Exceptions for SQL Browser, Default Port 1433, UDP Port 1434 5) Using Management Studio I can successfully connect to the MSSQL named instance from the app server 6) I can ping I MSSQL box from the app server 7) Read and implemented all steps in the MSDN post below: http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx Thanks for your help.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend