| Groups | Blog | Home |
vb.net upgrade : Strange Error
In addition to Herfried's comments, are you certain you referenced the Microsoft.VisualBasic.Compatibility namespace via "Project - Add Reference"? You can expand the References Node in Solution Explorer to see what assemblies you have referenced. Hope this helps Jay [quoted text, click to view] "Tym" <no_spam@ictis.net> wrote in message news:m3kcn09bt9amh48d27uqrifs491d01g4ql@4ax.com... > I've just downloaded the vb.net version of David Irland's blowfish > algorithm > > I used his VB6 versino quite sucessfully for password encryption. > > Moved up to vb.net and downlaoded the above. The projext as downloaded > works great! > > As with the VB6 version, I copied the modules into my own projext and > run it, to be greeted with errors: > > C:\Documents and Settings\Tym\My Documents\Visual Studio Projects\SICS > Control\basBlowfishFns.vb(140): Type 'VB6.FixedLengthString' is not > defined. > > > I have made sure that my project has the same references as the > downloaded one, but I still can't get the bugger to run!! > > HELP!! > > It doesn't like the VB6.FicedLengthString(x) dim statement..... > >
Tym,
Oh! one other thing to check is the Project level imports. Check to see if Microsoft.VisualBasic.Compatibility is listed under "Project - Properties - Common Properties - Imports" You may want to verify all the "Project - Properties" are set the same. Hope this helps Jay [quoted text, click to view] "Tym" <no_spam@ictis.net> wrote in message news:m3kcn09bt9amh48d27uqrifs491d01g4ql@4ax.com... > I've just downloaded the vb.net version of David Irland's blowfish > algorithm > > I used his VB6 versino quite sucessfully for password encryption. > > Moved up to vb.net and downlaoded the above. The projext as downloaded > works great! > > As with the VB6 version, I copied the modules into my own projext and > run it, to be greeted with errors: > > C:\Documents and Settings\Tym\My Documents\Visual Studio Projects\SICS > Control\basBlowfishFns.vb(140): Type 'VB6.FixedLengthString' is not > defined. > > > I have made sure that my project has the same references as the > downloaded one, but I still can't get the bugger to run!! > > HELP!! > > It doesn't like the VB6.FicedLengthString(x) dim statement..... > >
Tym,
Just realize that both are doing the same thing. That both are correct. "Project - Properties - Common Properties - Imports" is the same as putting "Imports Microsoft.VisualBasic.Compatibility" at the top of each source file. If you have 15 files in your project, but only 1 or 2 need Microsoft.VisualBasic.Compatibility, I would probably use Imports in each of those files, instead of Project Properties. FWIW: Over time I slowly remove uses of the Microsoft.VisualBasic.Compatibility namespace changing any Compatibility constructs with constructs from Microsoft.VisualBasic & the BCL (Base Class Library or Framework) instead. As the Compatibility namespace is intended more for upgraded projects, rather then new development. Hope this helps Jay [quoted text, click to view] "Tym" <no_spam@ictis.net> wrote in message news:5q0dn0d0fen4nl6qgc4qc7uhom8ug5229n@4ax.com... > On Wed, 20 Oct 2004 08:38:34 -0500, "Jay B. Harlow [MVP - Outlook]" > <Jay_Harlow_MVP@msn.com> wrote: > >>Tym, >>Oh! one other thing to check is the Project level imports. >> >>Check to see if Microsoft.VisualBasic.Compatibility is listed under >>"Project - Properties - Common Properties - Imports" >> >>You may want to verify all the "Project - Properties" are set the same. > > > BINGO!! > > That's the one.... removed the other import statements (see previous > post) and replaced with this one. now works!! > > Thanks > >
I've just downloaded the vb.net version of David Irland's blowfish
algorithm I used his VB6 versino quite sucessfully for password encryption. Moved up to vb.net and downlaoded the above. The projext as downloaded works great! As with the VB6 version, I copied the modules into my own projext and run it, to be greeted with errors: C:\Documents and Settings\Tym\My Documents\Visual Studio Projects\SICS Control\basBlowfishFns.vb(140): Type 'VB6.FixedLengthString' is not defined. I have made sure that my project has the same references as the downloaded one, but I still can't get the bugger to run!! HELP!! It doesn't like the VB6.FicedLengthString(x) dim statement.....
"Tym" <no_spam@ictis.net> schrieb:
[quoted text, click to view] > I have made sure that my project has the same references as the > downloaded one, but I still can't get the bugger to run!! > > HELP!! > > It doesn't like the VB6.FicedLengthString(x) dim statement..... Are you sure you imported the 'Microsoft.VisualBasic.Compatibility' namespace? \\\ Imports Microsoft.VisualBasic.Compatibility .. .. .. /// -- Herfried K. Wagner [MVP] <URL:http://dotnet.mvps.org/>
On Wed, 20 Oct 2004 14:27:48 +0200, "Herfried K. Wagner [MVP]"
[quoted text, click to view] <hirf-spam-me-here@gmx.at> wrote: >Are you sure you imported the 'Microsoft.VisualBasic.Compatibility' >namespace? Yes. Tried it in serveral locations.... AssembyInfo.vb from1.vb mod1.vb Still no joy... But.... now I've been tinkering.... I've put at at the top of both modules which refer to it and it seems to work OK now - thanks... Is that what I *should* have done?? :-)
On Wed, 20 Oct 2004 08:35:43 -0500, "Jay B. Harlow [MVP - Outlook]"
[quoted text, click to view] <Jay_Harlow_MVP@msn.com> wrote: >Tym, >In addition to Herfried's comments, are you certain you referenced the >Microsoft.VisualBasic.Compatibility namespace via "Project - Add Reference"?
On Wed, 20 Oct 2004 08:38:34 -0500, "Jay B. Harlow [MVP - Outlook]"
[quoted text, click to view] <Jay_Harlow_MVP@msn.com> wrote: >Tym, >Oh! one other thing to check is the Project level imports. > >Check to see if Microsoft.VisualBasic.Compatibility is listed under >"Project - Properties - Common Properties - Imports" > >You may want to verify all the "Project - Properties" are set the same. BINGO!! That's the one.... removed the other import statements (see previous post) and replaced with this one. now works!! Thanks
On Wed, 20 Oct 2004 11:26:36 -0500, "Jay B. Harlow [MVP - Outlook]"
[quoted text, click to view] <Jay_Harlow_MVP@msn.com> wrote: >Tym, >Just realize that both are doing the same thing. That both are correct. > >"Project - Properties - Common Properties - Imports" is the same as putting >"Imports Microsoft.VisualBasic.Compatibility" at the top of each source >file. > >If you have 15 files in your project, but only 1 or 2 need >Microsoft.VisualBasic.Compatibility, I would probably use Imports in each of >those files, instead of Project Properties. > >FWIW: Over time I slowly remove uses of the >Microsoft.VisualBasic.Compatibility namespace changing any Compatibility >constructs with constructs from Microsoft.VisualBasic & the BCL (Base Class >Library or Framework) instead. > >As the Compatibility namespace is intended more for upgraded projects, >rather then new development. > >Hope this helps >Jay Makes sense to me - maight include the import line in the modules that I need then I can just keep dropping them into the apps I need without
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
March 2007
April 2007
May 2007
July 2007
August 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |