I have an app using SQL Server Compact Edition. So I need the runtime to be on all the machines. I've been looking for the merge modules for the runtime however I've had no luck there.
Is there a way to bring the runtime into the app itself? And in so doing not not requiring the user to install the runtime?
Or is there a way of extracting the modules from the msi and loading them into my installer?
I am using Visual Studio 2012. And playing around with a few installer creators like Create install free. As a side, does anyone have a good freeware installer creator?
Any help would be great,
many thanks in advance
You can include the SQL Server Compact DLL files with your app, so you do not need to install anything in addition to your app - see my blog for long, detailed description - which SQL Server Compact version do you use?
Related
I have written code in C# .net framework 4.5. Now, the client says he wants it in Windows CE. So I have downloaded VS 2008 and created a smart device project with Windows CE option and framework 3.5. I have used the files as is and build. The solution gives lots of error on build.
Eg of error is - Background worker in .Net 4.5 is not supported in WinCE 2008 project
Any pointers how this can be achieved? Its a huge code so rewritting whole code will cost a lot. Quick pointers are highly appreciated.
I have tried removing the references from old proj and tried including dll from VS 2008 dlls. E.g. System.Data.SQL is not present in 2008. Background worker is not present in VS2008
Check out the Smart Device Framework, it provides a port of the Background Worker for the .NET Compact Framework. It may give you some alternatives for other pieces of code you're porting over:
https://github.com/ctacke/sdf
The missing SQL Server library is a difficult one to answer without more details, but you will need to decide on how you wish to access data. Is there going to be a local database or will you need to retrieve data from the SQL Server database through some type of service?
SQL Server Compact and SQLite are popular databases used on Windows CE, so those are some options if you need to create some sort of local database.
We are planning to create setup file for our project, our research lead us to:
InstallAwere 18
InstallShield 2013
We have some requirements that must be supported:
Windows Server 2012
Able to run other MSI/EXE
Full support for patches/updates
Run Powershell script
Database support (Create db/Execute sp)
Web site deployment
Nice to have:
- Windows features identification (run installation if necessary)
- Web installer (small package that will download all the necessary components)
Did I miss any other product on the market that can support all this? And the final question is what would you suggest for our setup package between these two?
Firsthand experience would be great.
Actually there is another application you can use for creating setup packages. It is Advanced Installer.
I'm using it for several years and it is really easy to use. I think it can help you with all of your requirements. They also have a great support team.
i think that InstallAware is more power full than InstallShield
look: http://www.installaware.com/compare-with-otherinstall-tools.htm
I developed windows service in visual c++ using VS2012. Usually I install it using sc create .... command for testing purpose. Now i want to create installer for my service using install shield limited. How can I do that? can anyone show me the steps to do that.
Thanks,
Khurram.
I guess your best bet is try to look up some InstallShield IDE tutorials as the installation package is created in a standalone IDE, but from my experience with InstallShield, Nullsoft and others I would recommend you take a look at WIX (http://wixtoolset.org/), it integrates with Visual Studio, creates a fully functioning MSI package and it is easy to do things like installing a service - take a look at an example here: How to install and start a Windows Service using WiX.
I developed a web-site on ASP.NET 3.5 SP1 platform. And additional I have 2 win services. My task is to build install package. I decided that Visual Studio install projects are not met my requirements. I design my own installer for this project, because I need to resolve many question and problem in install process. My problem: I need to deploy web-site into IIS, but I don't know how to do it easy. I found Microsoft tool as Web Deployment Tool, but I didn't find any documentation. And must I include this tool into my installer for deployment at destination customer? Another side I found SDC Tasks Library and it looks like a solution for me. But I saw many topics where people had problems and because the project was dead anybody couldn't help them. I know it is a long story... My question: how can I deploy the web-site from another program (I know that IIS versions have some differences and it is another headache), set a virtual directory, application pool (very important), a type of authentification and so forth ???
Thanks.
Use Wix for installers.
This article seems to cover what you want:
Automating Web deployment on IIS with WIX.
I am new to sharepoint and installshield. My responsiblity is to build and deploy the sharepoint solution as a package using istallsheild. Previously I was using solution package wsp and content database restoration. But now the client wants to deliver the total solution i.e. dlls, ascx files, xml files, servce files(.cs), feature files using installsjield from development server to another (test and/or client) server.
Can any body help me on this: how to do the sharepoint deployment using installshield?
thanks in advance.
I presume you are using SharePoint solutions to package dll's, ascx and xml files for deployment to a sharepoint server. These solutions are built using a tool like WSPBuilder.
If not: YOU SHOULD!
If so: Why not use SharePoint Installer? It is an installer wrapper around a .wsp (SharePoint solution) file. It will check for the existence of a sharepoint installation, if the required services are started etc.
For deployment to a test machine: Why would you need the .cs files? If you want to test (debug) code on a test machine, I suggest you use either continuous integration using a tool like CruiseControl.NET, or just install Visual Studio on the test machine (which I presume to be a dev test, not a client test machine) and get the latest version, do a build, then roll out the solution.
And what do you mean with "client" server? is there some windows app that's communicating with sharepoint included in the installer? If so, I suggest separating the SharePoint solution from the actual windows app. They might share DLL's but are not supposed to be in the same installer.
We are using a tool (open source - saf.codeplex.com) to automate the Sharepoint components using MSBuild/Features/STSADM etc. Recently they have upgraded this to use WIX so that we can deploy any SharePoint components.
saf.codeplex.com
It has got an very good documentation and also we got a good support in fixing and implementing the SharePoint automated deployment in our premise.
Thanks
BalamuruganK