Browse by Tags
All Tags »
Database (
RSS)
We have two sets of ASP.NET providers which currently exist; the ASP.NET SQL providers , and the ASP.NET Universal Providers . In VS 2010 the SQL providers were in only providers used for our project templates. In VS 2012 we have switched to using the Universal Providers. One of the drawbacks of the SQL providers is that it leverages DB objects of SQL server which are not available in SQL Azure. In our updated web publish experience we have an Update Database checkbox which can be used to incrementally publish the database to the destination database. In this case if the source connection string is used by the ASP.NET SQL providers and you are publishing to SQL Azure then you will see the following message on the dialog. Note: you may see the...
In Visual Studio 2010 we introduced a database publishing experience in the Package/Publish SQL (PP/SQL) properties page. This support relies on generating create scripts from the source database and then executing those scripts when you publish your web application. For more details regarding this feature take a look at Package/Publish SQL Tab, Project Properties . One of the negative aspects of the implementation that we have there is that the DB schema publishing is not incremental, it always executes create scripts. So in many cases you publish your app for the first time and things are great, but the next time you try to publish you receive errors because it tries to create DB objects which already exist. In our improved publish dialog...
We’ve been getting a few questions by our users about Visual Studio 2010’s support for SQL Server versions. So I thought it would be good to address them here (when one person asks a question, there are probably others thinking the same question.) Visual Studio 2010 only supports SQL Server 2005+ Visual Studio 2010’s design time data tooling only supports SQL Server 2005 (including express editions) or later. What this means is that you will not be able to connect through the Server/Database Explorer to any older versions of SQL Server or use any of the data design tools that require Visual Studio to connect to the database (LINQ designer, datasource wizard, table editing, etc.) This does not mean that your ASP.NET pages will stop working; the...
Dev10 Beta2 DB Deployment property page has some changes from Beta1. Please provide your valuable feedback for us to make it better for you. Thanks. 1. Tab page name changed from “Deploy/SQL” To “Deploy SQL” 2. Customer can use “Import from Web.config” button to import all the connection strings defined in root web.config to the database entries list. For example, if web.config contains the following connection strings: < connectionStrings > < add name = " ApplicationServices " connectionString = " data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true " providerName = " System.Data.SqlClient " /> < add name = " AdventureWorksConnection...
In Visual Studio 2010 Beta1 release, SQL server database schema and data can be packaged for deployment along with the website. It utilizes Msdeploy SQL Database provider functionality in IIS team’s msdeploy release. In Visual studio 2010 Beta1, user can set the database package options in web application project’s Deploy-SQL property page as following. User can add a package connection by clicking “Add” button and make sure it’s checked. To select the source database for package, one can check “Pull data from an existing database” check box, and select or enter the database connection string. In Beta1, only three packaging choices are provided for the database, “Schema only”, “Complete database” and “Exclude objects...
More Posts