Does anyone know if I can use SQL Server Compact Edition 3.5 on mono?
I'm hoping they are written as managed assemblies and will work ok..does anyone have any experience?
All of the SQL Compact (except System.Data.SqlCe.dll obviously) are native libraries, so no they won't work under non-Windows platforms.
Pretty replacement for SQL CE is SQLite
SQLite ADO.NET Provider is portable and exists on Microsoft.NET and Mono
http://sqlite.phxsoftware.com
http://www.mono-project.com/SQLite
native components is exists for most major platforms and source code also available
(By 'on mono' I assume you mean running on Mono in Linux?)
No. I'm pretty sure none of the SQL Server versions are built on managed assemblies.
Related
What I thought would be an easy google turned up no results. I'm trying to find out if Enterprise Library 4.1 is compatible with Windows Server 2008 SP2.
The system requirements say its compatible with Server 2008, but there is no mention of the service pack. Does anyone know definitively if these two are compatible?
Thank you for your time.
Typically compatibilities will list the minimum requirements; compatible with "Windows Server 2008" would include it and subsequent service packs (unless explicitly indicated otherwise). Keep in mind EL 4.1 was released almost a year before 2k8 SP2 was.
Does anyone know definitively if these two are compatible?
I guess it would depend on how you define "definitively" and "compatible". ;)
Do you want to know if Enterprise Library will run under Windows 2008 Server SP2? I don't believe that it was formally tested against that version (typically testing will go back two OS releases and SP2 didn't come out until the year after Enterprise Library was released) but it should work on later OS versions. For example, I have used version 4.1 with Windows 7.
As in title I'm having problem with my VB project when I change its .NET Framework from 4.5.1 in which I have application written to v4 which is supported on windowsXP. When I make the change and try to compile my program database could not be found. Should I make any extra changes in project properties or why database could not be found?
Thank you for help!
The Jet engine is not supported on 64bit machines. I know it is crazy but it's true. Not sure what MS Access uses on 64Bit, must be something else.
Jet on 64Bit
Some places say it's not going to be supported, others say it is part of Office 2010 install and you can download a seperate driver.
I ran into this when deploying a web app to our 64Bit server and just found a way around using MS Access for our report server. Got luck.
I'm a newbie to connect Oracle 10g using vb.net in MS Visual 2005. Please share me in coding.
You need to be more specific in your question because no one will write your project for you.
There are tons of resources on line to help you:
Using Oracle with VB.NET
If you're OK with being married to Oracle, a native driver is fastest. You tagged VS2005 so I assume you are deploying to .NET Framework 2.0. Our shop uses System.Data.OracleClient and it works fine (you will need the Oracle client installed on the target machine). This namespace, however, has been deprecated in the 4.0 framework release. The preferred way forward (which I've not tried yet) is either ODP.NET or another 3rd-party driver. This question details some of the alternatives.
There is a project I'm off to start and thinking of using SQL CE to keep resources small and anyway the data would be simple enough.
I was thinking and "heard" that there is a way that u can make your app play with SQL CE without installing the runtime, with adding some dlls and voila.
I would like to start using EF4 so it would be EF4 on SQL CE.
Any points, thought?
You can just deploy the binaries that can be found in the installed directory on your development PC - meaning anyone using your app doesn't need to run an MSI for it.
http://msdn.microsoft.com/en-us/library/aa983326(VS.80).aspx
I don't know much about EF4 and SQL-CE, but I spotted this after a short search:
http://thedatafarm.com/blog/data-access/a-few-sql-server-ce-and-entity-framework-gotchas/
Basic Question -
I have installed SQL Server Express 2008 with integrated SP1. This is the database engine alone.
I realise now that I also need the express studio in order to perform a few tasks. I have installed it, however I know that it was the original installer from before SP1 was released.
I have tried it and it appears to work fine but should I install SP1 / could something unforeseen happen in the future?
Some background! -
I wrote out the question and just realised that people probably don't care, so I just summed it up above!
After reading many different sites and guides, the install order for Visual Studio 2008 really confused me.
I really wanted to install SQL Server Express 2008 with advanced services, however on my other machine I had so many problems with it not being detected with Visual Studio, I just wanted an easy life!
I found the download from Microsoft that had SQL Server Express 2008 with SP1 integrated, however it was only the basic engine without any addons. (At the end of the day, as much as I wouldn't mind reporting services, I doubt I will need to use it any time soon).
I installed this, and after applying the hotfix (for x64 sql) my Visual studio can detect and use it no problem.
Now, I want to use Management Studio Express to write a few SQL scripts. The installer is obviously the original one. It seems to work fine, but I cannot find out any information - do I need to install SP1 for it?
Just install it, if its found something it can update - it will, if not... it won't....
Thanks to the wonder of Windows Installer (and I don't mean "I wonder why it's doing that?"--I mean like "This is wonderful!") it is unlikely that you have caused any big issues by running the older version afterwards.
So, yeah, you can probably just install the SQL 2008 Express Management Tools with no worries. If you want to be sure, afterwards just run the SP1 installer and it will make sure everything's up-to-date.
I always make sure to apply patches to client tools as well as server services. There is no reason to take the chance that your client tools have fallen behind in servicing.