SQL Compact Development
|
From: John R. Dougherty on 31 Jan 2008 18:24 In order to develop solutions with the SQL Server Compact version, must I use Visual Studio 2008, or is there a way to use Visual Studio 2003 or 2005? What about the version of SQL Server itself? Does it have to be at 2005 or 2008 to support the Compact version?
From: Christopher Fairbairn on 31 Jan 2008 18:36 Hi, "John R. Dougherty" <JohnRDougherty(a)discussions.microsoft.com> wrote in message news:A5480851-5FF5-4E9C-9497-F65ED5F5856F(a)microsoft.com... > In order to develop solutions with the SQL Server Compact version, must I > use > Visual Studio 2008, or is there a way to use Visual Studio 2003 or 2005? > What about the version of SQL Server itself? Does it have to be at 2005 > or > 2008 to support the Compact version? This depends upon which version you are talking about. Are you talking about SQL Server 2005 Compact Edition, or SQL Server Compact 3.5? (See a blog entry of mine called "The many versions of SQL Server CE" available at http://www.christec.co.nz/blog/archives/236) In general for a fully featured developer experience * Use VS2005 for v3.0 or v3.1 databases * Use VS2008 for v3.5 databases In a blog posting of mine called "Installing SQL Server Compact Edition (v3.1)" (available at http://www.christec.co.nz/blog/archives/253) I discuss what support/lack of support you will find in the various versions of Visual Studio. Essentially if you are happy manually adding a file reference to the System.Data.SqlServerCe assembly, and not being able to use any of the graphical tools (such as the Data Source Configuration Wizard) you can target older/newer versions of SQL Server CE with a given version of Visual Studio (assumming the runtime targeted by that version of Visual Studio is compatible with the assemblies). However if you want to use all the graphical database tools within Visual Studio you will need to make sure you use the database version supported by your version of Visual Studio. Hope this helps, Christopher Fairbairn
From: John R. Dougherty on 1 Feb 2008 10:35 Yes, this helps. But let me probe this a little more specifically - here is my dilemma: I developed a Visual Studio 2003 Pocket PC app for a client, which employs use of .CDB files (Pocket Access). This client has been forced to upgrade to ActiveSync 4.5 due to other applications, so now of course my application is no longer going to work since Pocket Access is not supported with the new version of ActiveSync. I am investigating the best options. Do you have any recommendations on this situation, and preferrably, I want to still use VS 2003? Is there going to be some transparent solution that I can use, or am I looking at re-writing the application for use with SQL? The client's handhelds are not Internet-active, so it still has to be a solution where data starts on a desktop application, syncs with the handheld, is updated on the handheld, and sync'ed back to the desktop. - Thanks, JRD "Christopher Fairbairn" wrote: > Hi, > > "John R. Dougherty" <JohnRDougherty(a)discussions.microsoft.com> wrote in > message news:A5480851-5FF5-4E9C-9497-F65ED5F5856F(a)microsoft.com... > > In order to develop solutions with the SQL Server Compact version, must I > > use > > Visual Studio 2008, or is there a way to use Visual Studio 2003 or 2005? > > What about the version of SQL Server itself? Does it have to be at 2005 > > or > > 2008 to support the Compact version? > > This depends upon which version you are talking about. Are you talking about > SQL Server 2005 Compact Edition, or SQL Server Compact 3.5? (See a blog > entry of mine called "The many versions of SQL Server CE" available at > http://www.christec.co.nz/blog/archives/236) > > In general for a fully featured developer experience > > * Use VS2005 for v3.0 or v3.1 databases > * Use VS2008 for v3.5 databases > > In a blog posting of mine called "Installing SQL Server Compact Edition > (v3.1)" (available at http://www.christec.co.nz/blog/archives/253) I discuss > what support/lack of support you will find in the various versions of Visual > Studio. > > Essentially if you are happy manually adding a file reference to the > System.Data.SqlServerCe assembly, and not being able to use any of the > graphical tools (such as the Data Source Configuration Wizard) you can > target older/newer versions of SQL Server CE with a given version of Visual > Studio (assumming the runtime targeted by that version of Visual Studio is > compatible with the assemblies). > > However if you want to use all the graphical database tools within Visual > Studio you will need to make sure you use the database version supported by > your version of Visual Studio. > > Hope this helps, > Christopher Fairbairn > >
|
Pages: 1 Prev: SetForegroundWindow crashes Next: reading a text/csv and displaying in table format |