From: Robert S. <fir...@bc...> - 2006-02-22 23:00:47
|
Perhaps I might be able to lend a little help on the DDEX front ... Here's a few changes to the reg file that should make Firebird packageless. Replace any occurrance of "VisualStudio" with "VWDExpress" to make the reg file work on that Express edition: ----- Cut Here ----- ÿþWindows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataSources\{2979569E-416D-4DD8-B06B-EBCB70DE7A4E}] @="Firebird Data Source" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataSources\{2979569E-416D-4DD8-B06B-EBCB70DE7A4E}\SupportingProviders\{92421248-F044-483A-8237-74C7FBC62971}] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}] @=".NET Framework Data Provider for Firebird" "DisplayName"="Provider_DisplayName, FirebirdSql.VisualStudio.DataTools.Properties.Resources" "ShortDisplayName"="Provider_ShortDisplayName, FirebirdSql.VisualStudio.DataTools.Properties.Resources" "Description"="Provider_Description, FirebirdSql.VisualStudio.DataTools.Properties.Resources" "CodeBase"="%Path%\FirebirdSql.VisualStudio.DataTools.dll" "InvariantName"="FirebirdSql.Data.FirebirdClient" "Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionSupport] @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionSupport" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionProperties] @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionProperties" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionUIControl] @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionUIControl" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataObjectSupport] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataSourceInformation] @="FirebirdSql.VisualStudio.DataTools.FbDataSourceInformation" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataViewSupport] ----- Cut Here ----- The changes above are to replace the FactoryService entry with Codebase, and specify the full path to the design-time DLL. The second change was to add class locations to many of the SupportedObjects. Not all of them need to be explicitly declared -- some of them are instantiated from FbDataConnectionSupport. Getting it to work in the other Express Editions is a little more complicated. Now then, as for the VSIP SDK requirement in order to get the DDEX packaged provider working ... Carlos, run right over to the http://www.vsipdev.com website and register there! Once registered, you can create a product and request a Package Load Key. Once you get a PLK granted, you can then add the PLK contents to the satellite DLL, and add a few more keys to the reg file, and then nobody will have to download the VSIP SDK in order to use the Firebird DDEX provider anymore. Furthermore, if you really want to get clever, you can do a neat little trick in FbDataConnectionProperties so that you no longer have to register the Firebird data provider in the GAC in order to use the designer. It requires some more reg file changes however. Robert |
From: Robert S. <fir...@bc...> - 2006-02-22 23:07:12
|
One other thing ... if you go packageless, you don't need the VSIP SDK either. That and supporting all the Express Editions are the primary reason I'm leaving the SQLite provider packageless. Robert |
From: <car...@te...> - 2006-02-23 14:42:03
|
Hello: > One other thing ... if you go packageless, you don't need the VSIP SDK > either. That and supporting all the Express Editions are the primary reason > I'm leaving the SQLite provider packageless. Thanks !!! I will see if i can get some time next week ( after Tuesday that is when finishes my actual daily job contract ) to see if can leave it as Package less ... -- Best regards Carlos Guzmán Álvarez Vigo-Spain |
From: Juan J. O. <jo...@th...> - 2006-02-22 23:46:24
|
""Robert Simpson"" <fir...@bc...> wrote: > Perhaps I might be able to lend a little help on the DDEX front ... > :) You did it!!!!! Thanks Juan Jose |
From: Rob H. <met...@gm...> - 2006-02-23 12:50:35
|
Apologies for the incomplete message earlier. I've modified the registry stuff for VWDexpress and I can now get to the proper connection dialog in VWD express but we I try to ok the connection I get the same error I used to get before: Field not found: 'System.Collections.Generic.KeyValuePair`2.Value' I'm using the assemblies I compiled from the 2.0 beta 4 sources. I've tried searching for anything relating to the value property but my guess is that its somewhere inside either the editor or the .net framework? Also the values for IsolationLevel or ServerType cant be set? Maybe this is related? Rob |
From: Robert S. <fir...@bc...> - 2006-02-23 14:35:16
|
A good place to start would be to run vwdexpress in a debugger so you can get the stack dump. That'd help Carlos identify where the error is coming from exactly. Robert ----- Original Message ----- From: "Rob Hutchison" <met...@gm...> To: <fir...@li...> Sent: Thursday, February 23, 2006 5:50 AM Subject: [Firebird-net-provider] Re:DDEX stuff Apologies for the incomplete message earlier. I've modified the registry stuff for VWDexpress and I can now get to the proper connection dialog in VWD express but we I try to ok the connection I get the same error I used to get before: Field not found: 'System.Collections.Generic.KeyValuePair`2.Value' I'm using the assemblies I compiled from the 2.0 beta 4 sources. I've tried searching for anything relating to the value property but my guess is that its somewhere inside either the editor or the .net framework? Also the values for IsolationLevel or ServerType cant be set? Maybe this is related? Rob |
From: Anthony K. <to...@re...> - 2006-03-07 21:51:01
|
Is it possible to integrate the Firebird .NET 1.7 Provider with DDEX? It is my understanding that non compliant .NET 2.0 Providers do not take advantage of the VS DDEX. Therefore all I have to do is install the executable, and place the assembly references in my web.config file. Is this correct? ""Robert Simpson"" <fir...@bc...> wrote in message news:004d01c63803$c6300150$b92...@CI...... > Perhaps I might be able to lend a little help on the DDEX front ... > > Here's a few changes to the reg file that should make Firebird > packageless. > Replace any occurrance of "VisualStudio" with "VWDExpress" to make the reg > file work on that Express edition: > > ----- Cut Here ----- > ÿþWindows Registry Editor Version 5.00 > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataSources\{2979569E-416D-4DD8-B06B-EBCB70DE7A4E}] > @="Firebird Data Source" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataSources\{2979569E-416D-4DD8-B06B-EBCB70DE7A4E}\SupportingProviders\{92421248-F044-483A-8237-74C7FBC62971}] > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}] > @=".NET Framework Data Provider for Firebird" > "DisplayName"="Provider_DisplayName, > FirebirdSql.VisualStudio.DataTools.Properties.Resources" > "ShortDisplayName"="Provider_ShortDisplayName, > FirebirdSql.VisualStudio.DataTools.Properties.Resources" > "Description"="Provider_Description, > FirebirdSql.VisualStudio.DataTools.Properties.Resources" > "CodeBase"="%Path%\FirebirdSql.VisualStudio.DataTools.dll" > "InvariantName"="FirebirdSql.Data.FirebirdClient" > "Technology"="{77AB9A9D-78B9-4ba7-91AC-873F5338F1D2}" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects] > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionSupport] > @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionSupport" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionProperties] > @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionProperties" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataConnectionUIControl] > @="FirebirdSql.VisualStudio.DataTools.FbDataConnectionUIControl" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataObjectSupport] > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataSourceInformation] > @="FirebirdSql.VisualStudio.DataTools.FbDataSourceInformation" > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\DataProviders\{92421248-F044-483A-8237-74C7FBC62971}\SupportedObjects\DataViewSupport] > ----- Cut Here ----- > > The changes above are to replace the FactoryService entry with Codebase, > and > specify the full path to the design-time DLL. > > The second change was to add class locations to many of the > SupportedObjects. Not all of them need to be explicitly declared -- some > of > them are instantiated from FbDataConnectionSupport. > > > Getting it to work in the other Express Editions is a little more > complicated. > > Now then, as for the VSIP SDK requirement in order to get the DDEX > packaged > provider working ... Carlos, run right over to the http://www.vsipdev.com > website and register there! Once registered, you can create a product and > request a Package Load Key. > > Once you get a PLK granted, you can then add the PLK contents to the > satellite DLL, and add a few more keys to the reg file, and then nobody > will > have to download the VSIP SDK in order to use the Firebird DDEX provider > anymore. > > > Furthermore, if you really want to get clever, you can do a neat little > trick in FbDataConnectionProperties so that you no longer have to register > the Firebird data provider in the GAC in order to use the designer. It > requires some more reg file changes however. > > Robert > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |
From:
<car...@te...> - 2006-03-07 22:24:16
|
Hello: > Is it possible to integrate the Firebird .NET 1.7 Provider with DDEX? =20 No. > It is=20 > my understanding that non compliant .NET 2.0 Providers do not take adva= ntage=20 > of the VS DDEX. =20 Correct. > Therefore all I have to do is install the executable, and=20 > place the assembly references in my web.config file. Is this correct? You mean to use the v2.0 of the provider ?? Or to integrate the provider=20 into Visual Studio 2005 ?? or Both ?? ;) --=20 Carlos Guzm=E1n =C1lvarez Vigo-Spain http://carlosga.blogspot.com/ |
From: Anthony K. <to...@re...> - 2006-03-07 22:41:59
|
Thanks for confirming. So to clarify on the 3rd point, I mean to use v1.7 of the provider. I already have v2.0 installed and integrated using the Simpson approach. I was considering going back to try using the 1.7 version. ""Carlos Guzmán Álvarez"" <car...@te...> wrote in message news:440...@te...... > Hello: >> Is it possible to integrate the Firebird .NET 1.7 Provider with DDEX? =20 > No. >> It is=20 >> my understanding that non compliant .NET 2.0 Providers do not take adva= > ntage=20 >> of the VS DDEX. =20 > Correct. >> Therefore all I have to do is install the executable, and=20 >> place the assembly references in my web.config file. Is this correct? > You mean to use the v2.0 of the provider ?? Or to integrate the > provider=20 > into Visual Studio 2005 ?? or Both ?? ;) > > --=20 > Carlos Guzm=E1n =C1lvarez > Vigo-Spain > > http://carlosga.blogspot.com/ > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Firebird-net-provider mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > |