With Silverlight 4 we get access to COM and with SQL CE 4.0 we get Entity Framework and nice little database server. I have a need for a standalone application (executing from a external jump drive) on a Windows machine without having to install any software. The requirement is that we cannot install any software on the target machine.
My thoughts are to develop a Silverlight out of the browser application, with SQL CE binaries included (not clear on how to accomplish) and run the application from the jump drive.
Does the solution make sense?
I found some pretty good information from the following MSDN link MSDN Private vs Central deployment for SQL CE and from Erik Ejlkov blog Everything SQL Server Compact which is really good, however the solution assumes that SQL CE is installed on the local machine.
Thanks
Related
I am developing desktop app using wpf mvvm,however I am confused as to how should I proceed with developing standalone application using sqlite,sql server compact etc
If you need a database (really need a database), I suggest using Entity Framework using the code first approach. This can create a local database for the application w/o the need of a database server.
However, strongly consider if you could just use files in the file system. It is amazing how much you can load into memory and if you want this to run on client machine, you likely don't have so much data that you can't just load the data into memory.
SQL Server Compact requires a separate installation step with administrative credentials.
SQLite is a library that can be compiled directly into the application.
In the case of .NET, it is a part of the System.Data.SQLite package, so it is automatically available when your application is shipped with this package (see SQLite deployment for .net application).
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.
We have an ASP.Net website running under the 4.0 framework in IIS 7.5 on a Windows Server 2008 R2 box. A portion of the web site functionality utilizes WCF and has a "standardEndpoints" section in the web.config.
The website works fine and everything works fine if we want to use the IIS Management Console GUI to do things.
We would like to use powershell to make changes to the web.site but when we run "Set-WebConfigurationProperty" an error is generated indicating that the "standardEndpoints" section of the web.config can't be processed.
The hotfix referenced here is not the solution. The website works, the hotfix appears to be only for Server 2008 (not R2), and when you try to install it, it says "not applicable for this server".
We did discover by running $PSVersionTable that PowerShell was referencing version 2.0 of the CLR. We installed Powershell 3.0 and now Powershell is referencing version 4.0 of the CLR but the problem persists.
We are looking to see if there is a simple solution to this. I suspect we may not have the right version of the IIS management script dll but can't find a different one to use. If the solution gets to complicated, we will just wipe the server and start from scratch.
Thanks for any suggestions,
John
I am considering switching to a co-located solution running a DNN (DotNetNuke) installation and an email server that mostly just does alias forwarding. I think I can get DNS services outside of this colocation box - but that could be an issue.
I am running this website for a non-profit group and trying to stay inexpensive. Will Windows Server 2008 Web Edition be acceptable for running all of this? My research so far says it will but I am looking for anyone with any experience running web edition and what sort of pitfalls does it have?
I was going to install SQL express as the backend for the DNN site. Indications are that you can't connect to SQL from outside the Web Edition box. Does this include SQL Management studio?
Any assistance or advice on this would be appreciated.
Update:
Still looking for any specifics with Windows Server 2008 Web Edition
We tried running DNN on Windows 2008 64-bit and 32-bit a while back. Not a great experience with intermittant failures and application hangs. We had to revert back to Windows 2003.
This was on a moderately loaded site. If you want to give them any sort of guaranteed uptime/availability I would recommend Windows 2003.