.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

App_Data - development vs production - SQLExpress

Posted By:      Posted Date: August 24, 2010    Points: 0   Category :ASP.Net

Help please, on mdf/ldf files manipulation between dev and prod App_Data folders.

My dev folder: ...\Visual Studio 2010\Projects\WebApplication1\
My prod folder: C:\inetpub\mywebsite\

There are 4 files in [dev]\APP_Data

The VS2010 publishing process copies the 4 files to [prod]\App_Data where my website users interact with them updating data therein.

Next time I publish, the files in [prod]\App_Data get overwritten, losing all current membership and app data changed by my website users.

I tried using SQL Server Management Studio, before publishing, to export current data from [prod]\App_Data\aspnetdb.mdf and myappdb.mdf, and import to [dev]\App_Data\aspnetdb.mdf and myappdb.mdf, but that brought up a bunch of detaching/attaching issues, ending up wiping out all security permissions settings of all the related files, even though I had used SQL Server Configuration Manager to stop the SQLExpress Service beforehand.

IIS Application Pool Identity:

App_Data mdf/ldf files security permission settings:
    SYSTEM: Full Control (dev/prod)
    NETWORK SERVICE: Read/Write (dev/prod)

View Complete Post

More Related Resource Links

File System Deployment from DEVelopment to PRODuction

Looking for best practices for doing an SSIS File System deployment from a DEV environment to a PROD environment using either Team System or strictly file based.

Development and Production Server software information for Sharepoint 2010 ??

Need to ask my IT Team to get me softwares for Development machines to write code / develop sites which we can give to end customers for deploying in their Sp2010 Production farm . W.r.t to that i have following questions : For Development , a) Which Windows Server 2008 OS version is sufficient - Standard , Enterprise , R2 ? b) Which SQL Server Version is sufficient ? c) Which VIsual studio version ? d) Which Sp2010 license version ?   From Production environment perspective , have following questions - a) What should be a recommendation to client for Production Server - Widows 2008Server sp2 or R2 ? SQL Server 2008 Server Sp2 or R2 ? Which is better and why ?  

Migrating changes from the Development to Production Site (SP2010, SPD and Visual Studio 2010)

Trying to find the best (least error-prone) approach to updating a live site containing content (based Documents and Tasks mainly) with changes. This got to be a common issue - a Development environment containing new features needs to be migrated over to production but the existing data and workflows with the associated tasks should be preserved. I found this thread http://social.msdn.microsoft.com/forums/en-us/sharepointdevelopment/thread/2C524797-9737-4D11-BE19-3E407C5C83CE which seems to provide a rather negative take on a tool-based approach but it's for older Sharepoint. Anything improved since then?

Making a copy of WSS3.00 from Production server to Development.

Dear All, I have a WSS3.0 production server which use MSSQL2008 database on Same box.Now I am planning to install a new server for developement purpose with same settings as production.Is it possibile to make a copy of production WSS on new Development server? It would be a great help if somebody can explain me the steps how to configure a copy of datas from Productin to Development incase if this option works!   Thanks to all in advance Regards Jo

In real time how Sharepoint site is deployed from Development to Production?

in our company we are directly working on Production site so we never got scenario to deploy Site to Production Server , so i want to know the procedure to deploy SP site to production Server. in real time do they use any tool to deploy? kindly provide information on this.

Deploying taxonomy term store and managed meta column from development machine to production machine

Hi, In my development environment, I created a taxonomy term store by importing a CSV file. I also created a site column of type "managed meta data" based on that term store. Now, I want to migrate to production environment. What is the best way to do this? When I generate the schema of my site column, it looks like this: <Field Type="TaxonomyFieldTypeMulti"    DisplayName="Article Type"    List="{d8b20e4f-ce12-4def-b59d-d44da2c13234}"    WebId="eef74e7c-a852-4c89-b811-e31b86853641"    ShowField="Path1033"    Required="FALSE"    EnforceUniqueValues="FALSE"    Group="Custom Columns"    ID="{47f78411-65fa-43c9-8cb8-68955aea1256}"    SourceID="{eef74e7c-a852-4c89-b811-e31b86853641}"    StaticName="Article_x0020_Type"    Name="Article_x0020_Type"    Version="4"    Mult="TRUE"    Sortable="FALSE"> <Default></Default> <Customization> <ArrayOfProperty> <Property> <Name>SspId</Name> <Value xmlns:q1="http://www.w3.org/2001/XMLSchema" p4:type="q1:string" xmlns:p4="http://www.w3.org/2001/XMLSchema-instance">99d

Deploying SSIS Package configurations in production and development


I'm working on a SSIS package which I want to deploy onto our development environment on a daily basis as I work on it. In addition, I want it to be easy to deploy to production. We're using xml configuration files for our packages, but I haven't seen anyone discuss the entire development process.

Do people keep their production and development configuration files in source control? If so, how? Are they part of your BIDS SSIS project? I tried adding them to "Miscellaneous". i.e. Example:

I have a project with the following SSIS Packages in it:




In the Miscellaneous folder I have:






I did this so I can keep them in source control. We don't use package deployment utilities, we just deploy by hand, but putting the files in Miscellaneous breaks the building of the deployment utilities because it attempts to copy the config files into the Deployment directory twice.


In addition, I set up the package configurations such that the

Deploying Publishing SharePoint site from development to test and production environment.




I have created a Publishing Site in SharePoint 2010, with pages created from custom page layouts, content types and Publish Content areas which I have created using SharePoint Designer 2010.

Also, I created custom Lists, Libraries and workflows in my development environment.

I want to replicate the site in test/production environment.

Can you please suggest me the best way to package all, along with custom site settings from development environment so that I can migrate small changes to test/ production environment later also without creating .wsp as I have access to SharePoint designer 2010 only.

Abhijit Sil

Dashboards appear slower in Production than in Development environment


Dashboards were created using PerformancePoint dashboard designer and were published to SharePoint Development environment. A backup of Devl site collection was taken and restored in Production. The dashboards appear to open slower in Production (close to a minute) than in Development (less than 5 secs) for the first time only. Subsequent response times are similar between Devl and Prod. The same code is executed in both environments.

Diferences between the two environments:
1. Development uses disk drives whereas Prod uses SAN drive.
2. Though the architecture (mentioned below) is different between Devl and Prod, the memory of the SharePoint, BI servers is the same - 64GB.

Development environment: There are two servers in the farm:
1. Windows 2008 x64 R2 server Enterprise, SQL 2008 R2 Enterprise with SSIS and SSAS, DBMS.
2. Windows 2008 x64 R2 server Enterprise, Excel services, PerformancePoint service, SQL 2008 R2 with SSRS, SharePoint Server 2010.

Production environment: There are multiple servers in the farm:
Business Intelligence:
1. Active/Passive SQL cluster with Windows 2008 x64 R2 server Enterprise, S

Code Optimized Web Development Profile (VS 2010 and .NET 4.0 Series)

When you first run VS 2010 it prompts you to select an IDE profile to use. The profile you select will configure how tool windows are displayed/docked in the IDE by default and set the default keyboard shortcuts. You can then customize any of these settings by using the Tools->Options menu within the IDE and then override/change them. You can also later reset your profile and pick a different one by choosing the Tools->Import and Export Settings menu command.

High-Performance .NET Application Development & Architecture

It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.

ASP.NET 4 and Visual Studio 2010 Web Development Beta 2 Overview

Many exciting changes for ASP.NET are coming in the .NET Framework version 4. This document gives an overview of many of the new features that are included in the Beta 2 release of the .NET Framework 4 and of Visual Studio 2010.

Logic behind N -Tier Application Development

In the arena of application development, developers all over the world use various programming languages, technical processes, and technical tools. While using number of technical & non technical elements the processes or methods become complex, for simplification of the application development process, developers use various techniques such as dividing the application architecture into layers or parts. In the professional & technical language this separation or division process is called N-Tier Application Development process, where "N" stands for number and "tire" stands for layers or parts.

Software Development Life Cycle (SDLC)

This is also known as Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall Method. This model has the following activities.

SDLC Approach or Software Development Life Cycle

SDLC process stats from conception to completion of any software project. According to this approach the software development team is responsible for the whole project development life cycle. After doing SRS and requirements analysis; developers follow different models of Software development Life Cycle (SDLC) available, while the most common model is SDLC waterfall model. They divide project in different stages & phases and the output of each stage or phase becomes the input for next stage.

System Development Life Cycle

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method), rapid application development (RAD), joint application development (JAD), the fountain model and the spiral model. Mostly, several models are combined into some sort of hybrid methodology

The Agile System Development Life Cycle (SDLC)

The goal of this article is to describe the agile system development life cycle (SDLC), putting it in context from what you may have heard about within the agile community and more importantly within the context of your overall IT efforts.
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