We've got a new poll up on our main web site page regarding the .Net data
provider so please weigh in with input.

http://www.elevatesoft.com

The issue that I'm running into is that the 100% managed provider is about
30% off the performance of the equivalent native Win32 code.  Given that we
have the ability to compile natively under WinCE and Windows, I'm trying to
figure out whether it is worth simply stubbing out the engine into an
un-managed DLL and just leaving the data provider layer as 100% managed
code.   Either way, the initial provider will be the 100% managed code
version, so you'll be able to see for yourself whether the performance is up
to par for your application.

--
Tim Young
Elevate Software
www.elevatesoft.com

SQL is Unmanaged, if MS are not not bother then you should not be too bothered either, also why not release both and let them choose speed\managed code.

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

We've got a new poll up on our main web site page regarding the .Net data
provider so please weigh in with input.

http://www.elevatesoft.com

The issue that I'm running into is that the 100% managed provider is about
30% off the performance of the equivalent native Win32 code.  Given that we
have the ability to compile natively under WinCE and Windows, I'm trying to
figure out whether it is worth simply stubbing out the engine into an
un-managed DLL and just leaving the data provider layer as 100% managed
code.   Either way, the initial provider will be the 100% managed code
version, so you'll be able to see for yourself whether the performance is up
to par for your application.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


I just realised this is open to misinterpretation. My reading is that "100% managed provider is about 30% off the performance" translates to it runs at 70% of the unmanaged version, but could be misread (if you read "of" instead of "off") it runs at 30% of the unmanaged version.

Roy Lambert