Re: Packaging MSDE in with Winforms C# app, using Windows packages
- From: "Jim Young" <thorium48@xxxxxxxxxxx>
- Date: Sat, 9 Apr 2005 09:52:17 -0700
It's a nice idea if your application is already written to use .Net. But in
my case our application is Win32 and installing the .Net framework just to
facilitate the installation of MSDE seem a bit too much. We've written our
own wrapper around the MSDE setup.exe to drive the MSDE installation.
Jim
"Paul Aspinall" <paul@xxxxxxxxxx> wrote in message
news:4tQ5e.44878$C12.21741@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the reply.
>
> I have now resolved this issue very satisfactorily.
> MS have a Deployment Toolkit for MSDE, that plugs directly in to Visual
> Studio. This provides an easy to use way of packaging your app with MSDE,
> and it works great.
>
> I would recommend anyone who has any issues or problems with this, to try
> using the MSDE Deployment Toolkit.
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=6e9a7403-c4ba-4d98-bb0b-2c9d6414071f&DisplayLang=en
>
> Thanks
>
>
> Paul Aspinall
>
> "Andrew D. Newbould" <newsgroups@xxxxxxxxxxxxxxxxx> wrote in message
> news:N4SjoPFv1mVCFwY4@xxxxxxxxxxxxxxxxxxxxxxxx
>> In message <h9RMd.6491$B8.6218@xxxxxxxxxxxxxxxxxxxxxxxxx>, Paul Aspinall
>> <paul@xxxxxxxxxx> writes
>>>Hi
>>>I want to package my C# winforms app, to be deployed with MSDE, as easily
>>>as
>>>possible for the end user.
>>>
>>>I want to create an MSI or Installshield (prefer MSI), to setup my C#
>>>app,
>>>together with MSDE (if not already installed), and the MSDE application
>>>DB.
>>>
>>>How can I detect if MSDE is already installed??
>>>
>>>Has anyone does this?? How??
>>>
>>
>> Everything I have found on the subject of packaging MSDE in your own MSI
>> or InstallShield package says "Just Don't Do It". It has many with
>> problems to deal with. This really only leaves two choices.
>>
>> 1. Include the standard MSDE package on your CD (or other Distribution
>> Media) and provide installation instructions which tell the user how to
>> install MSDE if required (remember the user might already have MSDE or
>> SQL Server installed and prefer to use that instance). In addition, you
>> would then need to provide a little setup / configuration program (or
>> embed it in your application) to Create the Database and associated
>> Tables etc. Obviously, this is a long winded method and can create plenty
>> of support calls / emails from the non computer literate.
>>
>> 2. The preferred method is to use the MSDE / SQL Server Deployment
>> Toolkit available for free download from MSDN. The includes a C# and
>> VB.Net examples plus full instructions to install (MSDE) and deploy your
>> database. This new customised package can then be called from your main /
>> normal MSI or InstallShield package during the installation process.
>>
>> I believe method 2 also can detect an existing instance to abort the
>> installation or install under a new named instance.
>>
>> As for detecting whether MSDE is already installed (ie: if using method 1
>> above), I think the simplest way would be to add a Custom Action to your
>> MSI / InstallShield package to check the existence of several know
>> registry keys under HKLM and HKCU.
>>
>> --
>> Andrew D. Newbould E-Mail: newsgroups@xxxxxxxxxxxxxxxxx
>>
>> ZAD Software Systems Web : www.zadsoft.com
>
>
.
- Prev by Date: Re: Workload Governor in MSDE 1.0 ?
- Next by Date: SQL SERVER DBA/ ATLANTA
- Previous by thread: Changing MSDE from Win NT authentication to Mixed
- Next by thread: SQL SERVER DBA/ ATLANTA
- Index(es):
Relevant Pages
|
