VS .NET 2005 Express + Mysql 5

[qu4dman]

Hi all

I would like to program an application with C# Express (for now,
because I'll soon use VS.NET 2005 not in "express version") that would
use Mysql 5 and Office 2007 in automation (Word, Excel, Access). I've
read about the Mysql 5.1 connector and plugin so I'll try it tonight.
I'd like to have your advice on the following ideas, please :

- Could my application be easily packaged and deployed (with all that
will be needed, such as the mysql 5 components) ? Even on XP machines
that don't have the .NET Framework 2 ?

- Could my application use the Office 2007 components on machines that
don't have Office 2007 installed ?

Thank you

 

[Peter Bradley]

XP machines that don't have .NET 2.0:

If you ain't got the Virtual Machine, you can't run the program.

Office 2007:

I would guess the same applies. If it ain't installed, you can't use it.

As for MySQL, you can use it just like SQL Server, except you use things
like MySqlConnection as opposed to SqlConnection. If you want your code to
be database agnostic you have a couple of choices. You could use an OleDB
connection, or (better, I think) could test a variable or perhaps something
in your config file on startup to determine which types to use. For example
you could write two DALs and call the appropriate one depending on the
contents of something in your App.config.

I even put the MySQL connector/.NET classes in my VS2005 toolbox.

HTH


Peter

 

[qu4dman]

XP machines that don't have .NET 2.0:

If you ain't got the Virtual Machine, you can't run the program.

Office 2007:

I would guess the same applies. If it ain't installed, you can't use it.

As for MySQL, you can use it just like SQL Server, except you use things
like MySqlConnection as opposed to SqlConnection. If you want your code to
be database agnostic you have a couple of choices. You could use an OleDB
connection, or (better, I think) could test a variable or perhaps something
in your config file on startup to determine which types to use. For example
you could write two DALs and call the appropriate one depending on the
contents of something in your App.config.

I even put the MySQL connector/.NET classes in my VS2005 toolbox.

HTH

Peter










- Afficher le texte des messages précédents -

Thank you very much for these informations.

I've choosen to develop the basics of the application under visual c#
express 2005, and as soon as we'll have a full vs.net 2005 I hope that
we'll be able to import our visual C# express project into it. Also
I've noticed, but maybe that's wrong, that one cannot package an
application for deployment under visual c# express.

For the db I'll use Access 2007 (Office 2007 in eval mode) and I hope
that this will not be a problem for the compatibility with lower
versions of office installed on our client's machines. I'll work in
compatibility mode (mdb db created in office 97/2003 mode).

I'll use Word automation from visual c# express 2005 to automate the
creation of word documents.

If you have any ideas or reflexions about all that...

Thanks again.

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I would like to program an application with C# Express (for now,
because I'll soon use VS.NET 2005 not in "express version") that would
use Mysql 5 and Office 2007 in automation (Word, Excel, Access). I've
read about the Mysql 5.1 connector and plugin so I'll try it tonight.
I'd like to have your advice on the following ideas, please :

- Could my application be easily packaged and deployed (with all that
will be needed, such as the mysql 5 components) ? Even on XP machines
that don't have the .NET Framework 2 ?

- Could my application use the Office 2007 components on machines that
don't have Office 2007 installed ?

..NET and Office requirements has already been discussed.

I just want to point out that MySQL Connector for .NET is GPL.

If your application is open source then no problem.

But if not then you need a commercial MySQL license to
distribute your app and the MySQL connector linked
together.

Arne

 

[Mark Rae [MVP]]

Could my application be easily packaged and deployed (with all that
will be needed, such as the mysql 5 components) ? Even on XP machines
that don't have the .NET Framework 2 ?

If you're using the CoreLab native .NET provider, yes:
http://www.crlab.com/mysqlnet/

It's been a while since I used MySQL, so can't confirm whether the latest
version of their in-house data provider will work on v1.x... ask them - try
it...

Could my application use the Office 2007 components on machines that
don't have Office 2007 installed ?

Depends how you want to do it... you can't automate something which doesn't
exist so, if you want to use the Office PIA, Office will need to be
installed...

If, however, you want to create Office documents without Office being
installed, Aspose is the way to go:
http://www.aspose.com/Products/Default.aspx

 

[Mark Rae [MVP]]

For the db I'll use Access 2007 (Office 2007 in eval mode) and I hope
that this will not be a problem for the compatibility with lower
versions of office installed on our client's machines. I'll work in
compatibility mode (mdb db created in office 97/2003 mode).

The Jet database format (.mdb) is already deprecated, and due to become
obsolete very soon:
http://www.vistadb.net/compare_jet.asp

Use another database file format if at all possible...

In fact, mainstream support for Access 2003 will come to an end in less than
18 months:
http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=Access+2003&Filter=FilterNO