Johan Nordberg

Have you had any experience with including SQL Server Express in a VSTO solution. I would much rather use that instead of Access, but then there's the whole issue of deploying that to the target machines.

Any suggestions




Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Dennis Wallentin

Hi Johan,

I wouldn't consider to add an SQL Server Express DB into a VSTO solution. Why isn't Access db an option I suspect that You don't want the end users be able to open the db through the 'backdoor'. One way is to create it with classic Visual Studio's Datatool where the db cannot be viewed via MS Access.






Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Johan Nordberg

Thanks for your reply.

Well, actually it's because I think Access is nothing but trouble compared to SQL Server. Error messages from the access drivers are a complete mess at best, it doesn't support FOR XML queries or reading XML, there's no support for Access with NHibernate. SQL Server is superior in every aspect, except that Access is really easy to deploy.

Why wouldn't you consider SQL Server Express The whole point of SQL Server Express is to allow file based databases. If I understand it correctly there's even an SQL Server Express redistributable that can be bootstrapped, but I know very little about it.






Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Dennis Wallentin

Johan,

I fully agree about the limitations of Jet MDBs (although some of them has been removed in Access 2007) and it's advantage when it comes to deployment. In my experience deployment of VSTO solutions is already difficult and by adding a SQL Server Express db the complexity of it increase. However, if You're comfortable with some of the standalone powerful tools for package & deployment like Wise then it would be a simple task . So in the end it's subject to Your knowledge and skillness with the deployment process.






Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Johan Nordberg

Yes, it's the deployment process that worries me. However, hopefully the deployment of SQL Server Express as a prerequisite shouldn't be that different from vsto runtime or the office pia's.

Maybe the .net access provider is better than the old mdac drivers and then maybe Access would be okay. But it drives me completely mad every time. Just a simple thing as using named parameters doesn't work correctly. You must have the parameters in the same order in the query and when you add them to the command object. And of course Access doesn't even recognize something's wrong. It's just silent and nothing works.

I guess there's only one way to find out. Smile

Btw, your blog posts about deployment is excellent. Keep up the good work. I'm really glad there's atleast one other swedish guy that work with VSTO. Smile






Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Dennis Wallentin

Johan,

Check out the Bootstrapper Manifest Generator

I guess there's only one way to find out.

In my experience we need to keep things simple with a well designed structure. In that way we, at least, can track down any errors.

Btw, your blog posts about deployment is excellent. Keep up the good work. I'm really glad there's atleast one other swedish guy that work with VSTO.

Tack sa mycket!






Re: Visual Studio Tools for Office Including SQL Server Express in VSTO solution

Johan Nordberg

>> In my experience we need to keep things simple with a

>> well designed structure. In that way we, at least, can track

>> down any errors.

I agree. But in my experience Access is neither well designed or simple.

Maybe it's because I worked so much with SQL Server (from version 6.5) that I find so much easier to work with. Or maybe it's just because SQL Server is better in every way when it comes to pure data access. Both indexes and relationships are really strange in Access. It's like you're not supposed to create good indexes.

It would be interesting to hear what others use as a database together with VSTO solutions.