I am trying to deploy a LightSwitch application to a hosted ASP.NET webserver in my company. The application access data stored on a SQL Server. My webserver admin is asking me if there are any special prerequisites needed for it to run. I've been reviewing the deployment guide
http://blogs.msdn.com/b/bethmassi/archive/2010/09/23/configuring-a-machine-to-host-a-3-tier-lightswitch-application.aspx
The article lists that there was a server component, but that it might change when RTM arrived:
NOTE: The team is looking at simplifying this process and possibly making the LightSwitch server component pre-reqs go away so this process will likely change for RTM.
This other MSDN article states that there are prerequisites.
http://msdn.microsoft.com/en-us/library/gg481779.aspx
My webserver admin keeps saying there's nothing to install on the ASP.NET web server other than .NET 4.0.
Am I missing something?
Server setup procedures haven't changed since Beta 1 (although of course the runtime has changed). It's pretty simple; the prerequisites article that you cited has the correct information. Basically the process is:
Install the Web Platform Installer if you don't already have it installed
Fire up the WPI and search for the LightSwitch runtime
Install!
As mentioned in the article, you'll need to decide whether you want to install a new instance of SQL Server locally with the prerequisites. If you've already planned for a production SQL Server, you'll want to choose the "without local SQL" option.
I don't have a specific answer, but I would stand up a VM with the appropriate version of windows server on it and run through an install on a do novo machine. Should confirm or deny what your server admin says . . .
Related
I'm trying to upgrade my TFS2017 Update 3 environment, to a new Azure DevOps Server (on-premise) environment.
I've created a new server for Azure DevOps Server, as I'd like a newer version of Windows Server, and in general just want a completely fresh environment. I took backups of my databases, shut down the old TFS2017, without deleting anything.
I migrated the databases to a new SQL Server instance (where I have all my other databases), as I see no need to use an SQL Server license just for source control.
Now comes the fun part. I tried to configure Azure DevOps Server to use the existing database (after the migration to the new SQL server instance was done). I had some issues with the TfsJobAgent service, but got those resolved.
I then tried to reconfigure Azure DevOps Server (as it failed the first time), but during configuration, it now tells me that data is corrupt, and that the existing database cannot be used. Good thing that I took backups :)
It should be said, that the new SQL server instance is a 2019 version, so that shouldn't be a problem.
I'm not quite sure what is happening here, and why it's giving me this error. Am I migrating in a wrong way? There's not much documentation out there describing this flow.
Please go through the documentation below before upgrade:
https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started?view=azure-devops
And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system requirements for TFS 2018. Upgrade SQL Server is
necessary for your scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and consistent set of database backups in case something
goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install the new version of TFS to get new binaries, and then run
through the upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from, you may need to configure each team project to gain access
to some of the new features made available.
I am not a SharePoint person so please bear with me on my question. I have been asked to install the SharePoint 2013 Client Component SDK in a production SQL environment. I have been trying to research if there are negatives to doing this and cannot find that this is a common thing to do. Since SDKs are usually used for development and in almost 20 years of managing SQL Servers I have never been asked to install SDKs in a production environment I am thinking that this is not a good idea. Anyone have advice? Thanks!
The Client SDK of SharePoint 2013 deploy DLLs in the GAG of your server.
Microsoft.SharePoint.Client.dll, Microsoft.SharePoint.Client.Runtime.dll (as far as i remember) and some others client DLLs. So, there should not be any conflict with other MS product.
But, this sdk is needed by client application for SharePoint. Which means, you need to install a client SharePoint Application on a SQL server. If there is no problem with this. There is no problem with your install of the SDK.
PS: Client application for SharePoint can connect To SharePoint system everywhere (server, PC,..) so you can install this apps on an other server (or PC). but it depends on what the application makes
(sorry for my english)
We have adopted WebDeploy for a new project and it seems to handle the deployment of our apps to our Dev and Test servers pretty well.
Now we would like to extend the use of WebDeploy to make it deploy database changes too.
Scott Gu's blogpost on webdeploy states:
Web Deploy enables you to not only
publish files – but also provision
database schema/data, run database
change scripts, set security ACLs, and
more
... but I can't find any good information on how to run database change scripts with
WebDeploy.
Does anyone have guidance, advice, best-practice or informative links for this?
Thanks
Darren.
If you're using Visual Studio 2010 or Visual Studio 2010 Express then you can specify database change scripts in the Package/Publish SQL tab in your project's properties. For more information see the following article:
How to: Deploy a Database With a Web Application Project
Hey, I've just finished writing a VB.NET application. Now I want to package the executable and the database ofcourse into a single installer file. I tried using QSetup, InstallShield to make SQL Server embedded into the setup file, and finally after hours of try&fail I have no idea. Anyone?
You can do a rightmouse on the properties of your Visual Studio Setup Project, and then there is this button 'Prerequisites'. There you can tick 'SQL Server Express ...' Or the 'SQL Server Compact 3.5'
link to image
You're probably best off just to set the connection file directly to the mdf, and attach it when the program is run. This is easier as it doesn't require a custom setup script to install the database to the database directory itself.
Note: Consider using the Compact Version, it's smaller, people don't like a full blown engine on their computer :)
InstallShield has a concept called Setup Prerequisites where you can teach it how to install additional packages along with your own. In older versions this would happen before calling your MSI. In newer versions you can have a "Feature" prerequisite where the prereq can associated to a feature and only installed if that feature is selected to be installed and after it's been selected but still before the main activity of your MSI occurs during the install execute sequence.
InstallShield also has a pattern for executing SQL scripts against your database instance so that you can then load your database into your newly installed instance.
All of this is quite powerful but it does take a bit of digging to learn.
As far as I know, anything but the SQL Server Compact Edition (SQL Server CE) cannot be embedded into your setup, really. Microsoft doesn't want that - you need to have SQL Server Express installed separately - any other edition can't even be shipped with your software (the client must have a license and installation separately).
You can indeed distribute SQL server with your custom application:
http://msdn.microsoft.com/en-us/library/bb264562(SQL.90).aspx
I have a WPF desktop application that uses a custom database for storage.
I need to prepare a setup project (from Visual studio 2008) (full setup, not ClickOnce).
I can add the to the list of prerequisites to the application and it does install during the setup of the application.
My question is: How can I run a script during the setup to create the database that the application needs? OR how can I restore the database to the client machine during the setup?
Another related question, what would happen if already exists on the client machine? How to detect the instance name and connection data? And then how to be able -if needed- to change the Connection string used by Entity framework to connect to that database?
Thanks,
Ed
SQL Server Express Edition is generally a really poor choice for a local database. It's a server-class engine that likes to use a lot of resources and runs as a service (so it's using up those resources even when your app isn't running). In other words, it belongs on a server.
The only place I've seen SQL Server Express used on a desktop that almost makes sense is as part of the Microsoft Small Business Accounting app, and in this case you generally install that program on a machine who's primary purpose is doing the accounting for your business.
What you should do is use a desktop or in-process class engine like SQL Server Compact Edition, Sqlite, or even Access. This will also greatly simplify your deployment.
If you insist on pushing through with this, know that the installer will create a new instance of sql server on the system. SQL Server will be fine with this. However, you'll need to account for that in the connection string of your app, and that can be a little more complicated. Additionally, to set up the database you have a couple options:
Create it from client code on first start of the app
Create it with a custom installer action (hard to get right because msi permissions)
Distribute an pre-build *.mdf file and attach with custom installer action or on first start of the app.