deployment of project migrating MSDE to SQLExpress

[Matt Fielder]

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress. I
am also potentially interested in migrating to using an installer built in
Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would be
helpful. The install needs to support a couple of different scenarios - ie:
a "server" install that installs and configures sqlexpress and a "client"
install that only installs program files and is able to pass command line
parameters to the .exe so that I can handle setting connection strings etc.
internally.
Any help would be greatly appreciated.

[aaron.kempf]

VB isn't supported under Vista; so who gives a shit?

they're going to discontinue VB.net soon I heard; I have a friend at
Microsoft that told me this.

Bill Gates was the big VB fanboy; and apparently he doesn't have the
BALLS to lead the industry anymore

-Aaron

Matt Fielder wrote:

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress. I
am also potentially interested in migrating to using an installer built in
Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would be
helpful. The install needs to support a couple of different scenarios - ie:
a "server" install that installs and configures sqlexpress and a "client"
install that only installs program files and is able to pass command line
parameters to the .exe so that I can handle setting connection strings etc.
internally.
Any help would be greatly appreciated.

[Ryan S. Thiele]

Funny, because I read that they are holding contests for programmers (VB and
C#) to program apps for Vista! Don't worry, Microsoft is not going to invest
time and tons of money for designers to design a platform, only to crush it.
VB will evolve, just like Basic, C++ ,C#, Windows, and all the other
platforms they design.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.com...
VB isn't supported under Vista; so who gives a shit?

they're going to discontinue VB.net soon I heard; I have a friend at
Microsoft that told me this.

Bill Gates was the big VB fanboy; and apparently he doesn't have the
BALLS to lead the industry anymore

-Aaron

Matt Fielder wrote:

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I
am also potentially interested in migrating to using an installer built in
Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be
helpful. The install needs to support a couple of different scenarios -
ie:
a "server" install that installs and configures sqlexpress and a "client"
install that only installs program files and is able to pass command line
parameters to the .exe so that I can handle setting connection strings
etc.
internally.
Any help would be greatly appreciated.

[aaron.kempf]

yeah.. that's why they're going to discontinue it

do you know how to read, jackass

VB marketshare has gone from 50% to 10% in the past 4 years; lick my
balls Microsoft

-Aaron
Ryan S. Thiele wrote:

Funny, because I read that they are holding contests for programmers (VB and
C#) to program apps for Vista! Don't worry, Microsoft is not going to invest
time and tons of money for designers to design a platform, only to crush it.
VB will evolve, just like Basic, C++ ,C#, Windows, and all the other
platforms they design.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.com...
VB isn't supported under Vista; so who gives a shit?

they're going to discontinue VB.net soon I heard; I have a friend at
Microsoft that told me this.

Bill Gates was the big VB fanboy; and apparently he doesn't have the
BALLS to lead the industry anymore

-Aaron

Matt Fielder wrote:

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I
am also potentially interested in migrating to using an installer built in
Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be
helpful. The install needs to support a couple of different scenarios -
ie:
a "server" install that installs and configures sqlexpress and a "client"
install that only installs program files and is able to pass command line
parameters to the .exe so that I can handle setting connection strings
etc.
internally.
Any help would be greatly appreciated.

[Ryan S. Thiele]

Install Lindows jackass. You hate microsoft. then don't use it. Simple.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@h54g2000cwb.googlegr oups.com...
yeah.. that's why they're going to discontinue it

do you know how to read, jackass

VB marketshare has gone from 50% to 10% in the past 4 years; lick my
balls Microsoft

-Aaron
Ryan S. Thiele wrote:

Funny, because I read that they are holding contests for programmers (VB
and
C#) to program apps for Vista! Don't worry, Microsoft is not going to
invest
time and tons of money for designers to design a platform, only to crush
it.
VB will evolve, just like Basic, C++ ,C#, Windows, and all the other
platforms they design.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.com...
VB isn't supported under Vista; so who gives a shit?

they're going to discontinue VB.net soon I heard; I have a friend at
Microsoft that told me this.

Bill Gates was the big VB fanboy; and apparently he doesn't have the
BALLS to lead the industry anymore

-Aaron

Matt Fielder wrote:

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I
am also potentially interested in migrating to using an installer built
in
Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user --
I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be
helpful. The install needs to support a couple of different scenarios -
ie:
a "server" install that installs and configures sqlexpress and a
"client"
install that only installs program files and is able to pass command
line
parameters to the .exe so that I can handle setting connection strings
etc.
internally.
Any help would be greatly appreciated.

[aaron.kempf]

I sure as fuck won't use Linux

why don't you C _FAGGOTS_ go and use Linux?

VB was more popular than any language named Java or C

why did Microsoft TAKE A DIVE AND KILL THE WORLDS MOST POPULAR
LANGUAGE?

it's not a VB problem

it's a security problem

killing VB6 isnt' going to solve all the worlds security problems;
probably make it worse since everyone has to RE-WRITE _EVERYTHING_

-Aaron


Ryan S. Thiele wrote:

Install Lindows jackass. You hate microsoft. then don't use it. Simple.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@h54g2000cwb.googlegr oups.com...
yeah.. that's why they're going to discontinue it

do you know how to read, jackass

VB marketshare has gone from 50% to 10% in the past 4 years; lick my
balls Microsoft

-Aaron
Ryan S. Thiele wrote:

Funny, because I read that they are holding contests for programmers (VB
and
C#) to program apps for Vista! Don't worry, Microsoft is not going to
invest
time and tons of money for designers to design a platform, only to crush
it.
VB will evolve, just like Basic, C++ ,C#, Windows, and all the other
platforms they design.

--
--
Thiele Enterprises - The Power Is In Your Hands Now!
--
<aa*********@gmail.comwrote in message
news:11**********************@j44g2000cwa.googlegr oups.com...
VB isn't supported under Vista; so who gives a shit?

they're going to discontinue VB.net soon I heard; I have a friend at
Microsoft that told me this.

Bill Gates was the big VB fanboy; and apparently he doesn't have the
BALLS to lead the industry anymore

-Aaron

Matt Fielder wrote:

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.
>
I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I
am also potentially interested in migrating to using an installer built
in
Visual Studio.
>
I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user --
I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be
helpful. The install needs to support a couple of different scenarios -
ie:
a "server" install that installs and configures sqlexpress and a
"client"
install that only installs program files and is able to pass command
line
parameters to the .exe so that I can handle setting connection strings
etc.
internally.
>
>
Any help would be greatly appreciated.

[Kevin Yu [MSFT]]

Hi Matt,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need to migrate to VS.NET setup
project from InstallShield. Also, you need to include SQL Server 2005
Express Edition in the setup project. If there is any misunderstanding,
please feel free to let me know.

In a setup project or ClickOnce deployment, you can add Prerequisites to
the application. When the prerequisites are not detected, the setup project
or ClickOnce will try to install them. After installation, you can run
certain scripts to configure the SQL Express. Here is some reference:

http://msdn2.microsoft.com/en-us/library/h4k032e1.aspx

In this case, there are two scenarios. In a setup project, the size of a
SQL Express package is about 34MB. The package is installed when needed,
but downloaded always. The Setup project does not support download when
needed option.

Otherwise, you can try to use ClickOnce deployment. When it detects that
certain prerequisites are not installed, it will try to download the setup
package from a location you specified. Thus minimizes the download size.
For more information about ClickOnce, please check the following link:

http://msdn2.microsoft.com/en-us/library/wh45kb66.aspx

If anything is unclear, please feel free to reply to the post.

Kevin Yu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Cor Ligthert [MVP]]

Matt,

In addition to Kevin, there are no other differences between using MSDE and
SQLExpress (beside connection string) than that SQLExpress is thousand times
easier to install, than MSDE was. (You can use SQLExpress as well in a kind
of Access way with a not enclosed database but that was not your question).

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:Ob*************@TK2MSFTNGP02.phx.gbl...

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I am also potentially interested in migrating to using an installer built
in Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be helpful. The install needs to support a couple of different
scenarios - ie: a "server" install that installs and configures sqlexpress
and a "client" install that only installs program files and is able to
pass command line parameters to the .exe so that I can handle setting
connection strings etc. internally.
Any help would be greatly appreciated.

[aaron.kempf]

Cor

I love that feature.

I wish that it was better advertised; better understood.. and native to
vista

-Aaron

Cor Ligthert [MVP] wrote:

Matt,

In addition to Kevin, there are no other differences between using MSDE and
SQLExpress (beside connection string) than that SQLExpress is thousand times
easier to install, than MSDE was. (You can use SQLExpress as well in a kind
of Access way with a not enclosed database but that was not your question).

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:Ob*************@TK2MSFTNGP02.phx.gbl...

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I am also potentially interested in migrating to using an installer built
in Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user -- I
use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be helpful. The install needs to support a couple of different
scenarios - ie: a "server" install that installs and configures sqlexpress
and a "client" install that only installs program files and is able to
pass command line parameters to the .exe so that I can handle setting
connection strings etc. internally.
Any help would be greatly appreciated.

[Matt Fielder]

Thanks for the reply Cor... Looks like I'm getting a lot of good information
here.

Ease of use and updating to more current standards are other reasons for
changing to SQLExpress. I've picked up a "Beginning SQL Server 2005
Progamming" from Wrox to try and get an idea of some of the differences ...
I'm hoping that 90% of my stuff will just work after converting the DB. My
use of the DB engine really is pretty simplistic, just tables, views and
stored procedures. No triggers or automated backups or things of that
nature are in use. I do know already there are a few changes that need to
be made - such as my CreateDatabase script probably won't work. I provide
backup and restore capabilities that I manage via scripting and that will
probably have to change as well.

You did mention that SQLExpress can be used in an Access sort of way. I
also seem to remember that it's possible to just use a path to a data file
in the connection string. ... does this mean that it's possible to simply
distrubute a data file and not need to install the engine on customers
machines?

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:O0**************@TK2MSFTNGP03.phx.gbl...

Matt,

In addition to Kevin, there are no other differences between using MSDE
and SQLExpress (beside connection string) than that SQLExpress is thousand
times easier to install, than MSDE was. (You can use SQLExpress as well in
a kind of Access way with a not enclosed database but that was not your
question).

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:Ob*************@TK2MSFTNGP02.phx.gbl...

>First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I am also potentially interested in migrating to using an installer built
in Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user --
I use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be helpful. The install needs to support a couple of different
scenarios - ie: a "server" install that installs and configures
sqlexpress and a "client" install that only installs program files and is
able to pass command line parameters to the .exe so that I can handle
setting connection strings etc. internally.
Any help would be greatly appreciated.

[aaron.kempf]

no; I believe that the user still requires SQL Express.

but you just don't necessarily have to register a database; you can use
it as a 'user instance' I hope that is the correct phrase


Matt Fielder wrote:

Thanks for the reply Cor... Looks like I'm getting a lot of good information
here.

Ease of use and updating to more current standards are other reasons for
changing to SQLExpress. I've picked up a "Beginning SQL Server 2005
Progamming" from Wrox to try and get an idea of some of the differences ...
I'm hoping that 90% of my stuff will just work after converting the DB. My
use of the DB engine really is pretty simplistic, just tables, views and
stored procedures. No triggers or automated backups or things of that
nature are in use. I do know already there are a few changes that need to
be made - such as my CreateDatabase script probably won't work. I provide
backup and restore capabilities that I manage via scripting and that will
probably have to change as well.

You did mention that SQLExpress can be used in an Access sort of way. I
also seem to remember that it's possible to just use a path to a data file
in the connection string. ... does this mean that it's possible to simply
distrubute a data file and not need to install the engine on customers
machines?

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:O0**************@TK2MSFTNGP03.phx.gbl...

Matt,

In addition to Kevin, there are no other differences between using MSDE
and SQLExpress (beside connection string) than that SQLExpress is thousand
times easier to install, than MSDE was. (You can use SQLExpress as well in
a kind of Access way with a not enclosed database but that was not your
question).

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:Ob*************@TK2MSFTNGP02.phx.gbl...

First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I am also potentially interested in migrating to using an installer built
in Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user --
I use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be helpful. The install needs to support a couple of different
scenarios - ie: a "server" install that installs and configures
sqlexpress and a "client" install that only installs program files and is
able to pass command line parameters to the .exe so that I can handle
setting connection strings etc. internally.
Any help would be greatly appreciated.

[Cor Ligthert [MVP]]

No the user needs the engine but you can deploy that seperately.

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:e8**************@TK2MSFTNGP03.phx.gbl...

Thanks for the reply Cor... Looks like I'm getting a lot of good
information here.

Ease of use and updating to more current standards are other reasons for
changing to SQLExpress. I've picked up a "Beginning SQL Server 2005
Progamming" from Wrox to try and get an idea of some of the differences
... I'm hoping that 90% of my stuff will just work after converting the
DB. My use of the DB engine really is pretty simplistic, just tables,
views and stored procedures. No triggers or automated backups or things
of that nature are in use. I do know already there are a few changes that
need to be made - such as my CreateDatabase script probably won't work. I
provide backup and restore capabilities that I manage via scripting and
that will probably have to change as well.

You did mention that SQLExpress can be used in an Access sort of way. I
also seem to remember that it's possible to just use a path to a data file
in the connection string. ... does this mean that it's possible to simply
distrubute a data file and not need to install the engine on customers
machines?

"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:O0**************@TK2MSFTNGP03.phx.gbl...

>Matt,

In addition to Kevin, there are no other differences between using MSDE
and SQLExpress (beside connection string) than that SQLExpress is
thousand times easier to install, than MSDE was. (You can use SQLExpress
as well in a kind of Access way with a not enclosed database but that was
not your question).

Cor

"Matt Fielder" <mf****************@nospam.nospamschreef in bericht
news:Ob*************@TK2MSFTNGP02.phx.gbl...

>>First off, if this is better posted in another group that qualifies as a
manged group, please let me know.

I currently have an application written in VB.Net using MSDE as the
database. Current install is via InstallShield. As I've just found out
that MSDE is not supported under Vista, I need to migrate to SQLExpress.
I am also potentially interested in migrating to using an installer
built in Visual Studio.

I have a few questions:
Are there any "best practices" for migrating from msde to sqlexpress?
As this is a downloadable trial application, I need to minimize download
size -- suggestions for doing so? Is it possible to configure so that
SQLExpress and the .Net framework are only downloaded on an as needed
basis?
The configuration for SQL Express needs to be transparent to the user --
I use a specific instance with a sa password unknown to users.
Getting started with creatign installs via Visual Studio documents would
be helpful. The install needs to support a couple of different
scenarios - ie: a "server" install that installs and configures
sqlexpress and a "client" install that only installs program files and
is able to pass command line parameters to the .exe so that I can handle
setting connection strings etc. internally.
Any help would be greatly appreciated.

[Kevin Yu [MSFT]]

Hi Matt,

I agree with Cor, that although we can redistribute the database file, it
still requires the SQLExpress engine to run.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[aaron.kempf]

kevin

well I said it before cor.. so why don't u admit you agree with me,
microslut

-Aaron


Kevin Yu [MSFT] wrote:

Hi Matt,

I agree with Cor, that although we can redistribute the database file, it
still requires the SQLExpress engine to run.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)