Greg,

<< Sorry for the delay in this but I have been out of the office.

I have sent the keys as requested. >>

Thanks.   Everything is in order there.

I just tried the DAC-TRIAL of 2.01 again, and I can get everything to work
in VS2005 by doing the following:

1) Install the trial
2) Modify the machine.config so that the assembly path references the
edbprovider (.NET) sub-directory instead of the edbproviderwm (.NET CF)
directory

It works every time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Just a thought but could this be anything to do configuration on 64 bit
machines?

Greg, what spec. is your machine?

Chris Holland

Tim Young [Elevate Software] wrote:
> Greg,
>
> << Sorry for the delay in this but I have been out of the office.
>
>  I have sent the keys as requested. >>
>
> Thanks.   Everything is in order there.
>
> I just tried the DAC-TRIAL of 2.01 again, and I can get everything to work
> in VS2005 by doing the following:
>
> 1) Install the trial
> 2) Modify the machine.config so that the assembly path references the
> edbprovider (.NET) sub-directory instead of the edbproviderwm (.NET CF)
> directory
>
> It works every time.
>

Chris,

<< Just a thought but could this be anything to do configuration on 64 bit
machines? >>

It's certainly possible.

--
Tim Young
Elevate Software
www.elevatesoft.com

Guys,
My laptop is a HP Compaq nc8430.
Intel Centrino Duo 2.00Ghz, 2.00 GB of RAM.

OS is Windows XP Professional 5.1.2600, SP2 build 2600
My collegue is running the same configuration.

Visual Studio is VS2005, Version 8.0.50727.42.
.net framework version 2.0.50727 SP1.


Could this perhaps be a security issue?

Thanks,
Greg

Greg,

The OS, etc. all check out.

<< Could this perhaps be a security issue? >>

Only if you installed the product to a network drive (which you didn't, by
what you've shown).  On a local drive on Windows XP, there shouldn't be any
problems.  Our installations require Administrator installation privileges
also, so even Vista shouldn't be an issue.

Could you do me one more favor ?  Could you search your local drive to make
sure that there aren't any local copies of the Elevate.ElevateDB.Data.dll
assembly in any of your VS project sub-directories.  Perhaps there's an
issue with VS grabbing the wrong assembly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,
I have 2 copies of this file:

C:\Program Files\ElevateDB DAC Trial\Version 2\assemblies\edbprovider
C:\Program Files\ElevateDB DAC Trial\Version 2\assemblies\edbproviderwm

Regards,
Greg

Hi All,

i have the problem here. I Tryed to use elevateDB trial on my Notebook with WinXP and on my Desktop PC with Vista and get the same
Errormessage. I also tryed the Workaround with the Machine.config without a result.

Stephan

Greg,

<< I have 2 copies of this file:

C:\Program Files\ElevateDB DAC Trial\Version 2\assemblies\edbprovider
C:\Program Files\ElevateDB DAC Trial\Version 2\assemblies\edbproviderwm >>

That is correct.  The first is the normal desktop .NET data provider, and
the second is the Windows Mobile .NET CF data provider.  The machine.config
entries should all be referencing the path to the desktop .NET data
provider.

--
Tim Young
Elevate Software
www.elevatesoft.com

Stephan,

<< i have the problem here. I Tryed to use elevateDB trial on my Notebook
with WinXP and on my Desktop PC with Vista and get the same Errormessage. I
also tryed the Workaround with the Machine.config without a result. >>

I'm not sure what the issue is.  The only problem with the installation is
the wrong path with the 'wm' appended, and once that is corrected,
everything works fine here, both with VS2005 and VS2008.

--
Tim Young
Elevate Software
www.elevatesoft.com

Greg,

The fix for the installation is available now in 2.01 B3.   Did you try it
yet to see if the issue is resolved ?  It shouldn't be any different than
what you tried manually, but you never know.

--
Tim Young
Elevate Software
www.elevatesoft.com