I am newer to Visual Studio 2012 and MVC4, and have a development project of a website using C# and MVC4 and SQL server 2012.
The Publish using web deploy works for the website portion of the project, but it does not automatically update the database portion (schema). If I right click the database portion of the project in VS2012 and click Publish, then the database schema is updated properly. I am only interested in schema updates. What could be wrong?
I programmed my development system to use Web Deploy 3.0. Here is a summary of my configuration:
Computer running win8 x64
SQL Express 2012 as my database server, running as the default instance (i.e. at localhost, NOT as .\SQLEXPRESS)
IIS Express 8 as my webserver, using the "Default Web Site" site (localhost)
Visual Studio 2012 Pro using MVC4 and C#
Web Deploy 3.0
The latest dates are all applied to the software
I programmed an SQL server user WDeployAdmin for managing the database updates and gave it full permissions over the database being used for the website. I also tried using Integrated Security (my administrator login) but that does not help.
I can correctly update the Default Web Site (views and controllers etc) using the Publish feature in VS2012 which uses Web Deploy 3.0.
When I use the Test Connection feature of the publishing setup options, it correctly connects to the database, and that certainly works fine when I do a separate Publish DB operation (right-click DB project, click Publish, and then pick my profile) for that part of my project.
So why doesn't the standard website Publish feature include the database schema updates? The standard website Publish always shows an empty change to database when the schema changes (e.g. a table or a stored procedure).
I have read through much MS docs but nothing is apparent to me.
Any help is appreciated,
Bruce
Related
We are developing a small application that needs to have a local database installed on each users computer that will then sync up to the main database, via web services etc...
Anyways when we deploy the application on the users computer we want to use clickonce deployment. Now I have used this before but not attaching a SQL Server database. I know you can go to prerequisites in clickonce properties and click SQL Server Express.
Now the question is, when you have created your .mdf database file including stored procedures and all - how do you get this attached and setup automatically in the local database that is just installed through clickonce?
Also once this is finished in the future we may want to run updates to the database on the clients machines. We would like to use clickonce for this to publish database updates. Obviously we don't want to overwrite the database and just publish the latest updates based on if they already have the database or not and what version they have.
How could this be achieved using clickonce? Thanks
I have developed SSIS Package to fetch data from SharePoint Lists and importing to the SQL Server Tables. I am going to deploy this package as a Project Deployment Model.
From these SQL Tables, I have built SSRS Reporting Solution including few reports and Deployed it on my Development SharePoint Site.
But now, I have no idea how to send this solution with reports to the Client Side.
I have checked below utilities but not getting the exact idea of what I should do.
http://rsbuild.codeplex.com/
http://msdn.microsoft.com/en-us/library/ms162839%28v=sql.110%29.aspx
SQL Server version I am using is SQL Server 2012 and Data tools version is also 2012.
Please guide me here.
Thank you,
Mittal.
To deploy your reporting objects, you right-click on the project in Visual Studio then select deploy and configure the server to deploy to.
If you are trying to get an already deployed package, you can use the import wizard:
e.g.
http://msdn.microsoft.com/en-us/library/hh270294.aspx
Then the report server can be accessed by the client browser - e.g. in internet explorer, browse to to: http:
//reportserver/reports
Where "reportserver" can either be the server's ip address or reporting server name.
You can also modify these reports using the report builder tool, that will allow you to edit the rdl files on the server - e.g. when you browse to the reports, you can select edit with report builder.
If you are using sharepoint, you can use sharepoint authentication mode or you can set up access based on active directory groups at the folder level, if the client is browsing to the reports using the web browser.
I'm actually done doing the small-scale application for our office, however, I really don't have any idea how to deploy this one. Can someone provide me any links on how to do this? This project will be deployed in one pc.
If its a Windows application you need to create a setup project.
If its a web based application, install your application on your web server and provide clients with the appropriate link.
I have developed a application in c# which is windows based application. It stores data into database sql server. I want to know, when I create setup in VS and install it in a client computer should I install sql server software also or Is there any way without installing SQL Server in client's PC My application can function correctly.
sIf you use a filebased implementaion of SQL (localDB) you should be able to get away with a "setup" installing the neccecary dependencies to bootstrap the DB. (Someone correct me?)
If you use the DB in a hosted SQL environment (SQL Server running as a service), you will need to install SQL server on the deployed pc, and get the database up.
I am no sure if you can "automate" installing SQL server and getting the DB up from a setup app.
You have two deployment options for applications that contain SQL Server Compact 3.5 databases. The method of deployment you choose depends on the servicing requirements of your application and whether your users will need administrative credentials on the computer on which the application will be installed.
Following are the deployment options for SQL Server Compact 3.5 databases:
1. Traditional Microsoft Windows Installer (Microsoft setup technology)
a. Users need administrative credentials to install the application.
b. SQL Server Compact 3.5 will be serviced by Microsoft Update.
c. Can use ClickOnce deployment.
-or-
Private file–based deployment (deploying the SQL Server Compact 3.5 DLLs as part of the project)
1. Users do not need administrative credentials to install the application.
2. SQL Server Compact 3.5 will not be serviced by Microsoft Update.
3. Can also use ClickOnce deployment.
I have to modify an ASP.NET Web Forms application which is currently on production on a Windows Server 2003 in II6.
The problem is that I didn't develop the application and there is not anymore the Visual Studio solution used to develop the application. Moreover the application lies under a website where other applications are running and the connection strings are stored in the global web config file.
I want to modify the application without compromising the version that is actually online.
How can I bring the production version back into a solution file? Many thanks