|
|
|
Rank: Member
Groups: Member
Joined: 8/18/2006
Posts: 28
Points: 15
|
We've been using VistaDB 3.3 Build 57 and decided to upgrade our application to use VistaDB 3.5 Build 84. As soon as I remove the old VistaDB 3.3 reference and add the new VistaDB 3.5 reference we get plently of "'File' is not a member of 'IO'" errors, even though "System" is an imported namespace. We are using VS 2008 SP1. I have tried cleaning the solution and rebuilding with no luck. If I change the reference back to 3.3 then the errors go away. I unistalled VistaDB 3.3 and 3.5, then reinstalled 3.5 and still the same problem. I made sure that 3.5 was the only VistaDB reference in the GAC. The application is a .NET 2.0 WinForms. Any ideas?
Regards,
Justin
|
|
|
|
Rank: Member
Groups: Member
Joined: 10/19/2006
Posts: 85
Points: 50
Location: 3rd Planet
|
I've experienced the same problem, my solution was to replace IO.File with System.IO.File. I only had a bit less than 30 errors of this kind, but some projects can contain a lot more than that, in which case it can turn out to be a real pain... maybe the VistaDB namespace contains a .IO that conflicts with System.IO ? 
- El pipo
|
|
|
|
Rank: VistaDB Staff
Groups: Administration, VistaDB Staff
Joined: 8/13/2006
Posts: 3,633
Points: 5,124
Location: Mount Dora, Florida
|
Pipo could be right. The obfuscation tries to use 2 letter abbreviations. System.IO is the correct using. I don't ever see anyone reference using IO (even though you can). I always go for the complete namespace reference in the using. It gives you a complete chain to explicitly declare what your intent was, and since it is so small (and is only done once). Jason Short
|
|
|
|
Rank: Team VistaDB
Groups: Member, Team VistaDB
Joined: 9/15/2008
Posts: 118
Points: 330
Location: Baltimore, MD
|
We use Resharper, and on build 84 it's finding the namespace "@if" which it is tending to want to look in when we start typing a favorite logic keyword. I'm not sure why we're seeing all of these types if they're internal/private types, but with Resharper we are. Kendall Miller Principal & Co-Founder - Gibraltar Software Blog | Gibraltar Software
|
|
|
|
Rank: Member
Groups: Member
Joined: 8/18/2006
Posts: 28
Points: 15
|
Added System to every IO reference sorted the problem. Is this issue going to be looked at in one of the next builds? Not that I'm going to go undo 100+ IO changes  Cheers
|
|
|
|
Rank: VistaDB Staff
Groups: Administration, VistaDB Staff
Joined: 8/13/2006
Posts: 3,633
Points: 5,124
Location: Mount Dora, Florida
|
Not really. It is a namespace issue. You would have the same problem with any application that had an IO namespace. That is why you should be explicit in the using statement. We have asked the obfuscation vendor for the ability to exclude certain letter codes from the short names (GC, IO), or to let us put a base to the shortened names. Jason Short
|
|
|
|
Rank: Member
Groups: Member
Joined: 7/1/2008
Posts: 21
Points: -1
|
Hello,
is there anything news from obfuscation-namespace-problem?
Best regards, Mario
|
|
|
|
Rank: VistaDB Staff
Groups: Administration, VistaDB Staff
Joined: 8/13/2006
Posts: 3,633
Points: 5,124
Location: Mount Dora, Florida
|
Nope, we have not gotten any updates from our provider at this point. We will ping them again. Since they seem to randomly pick their base names at each build it won't happen in every build... It is dumb luck that it happened that time. But as long as they allow 2 letter combinations only without a prefix it is bound to happen again. Jason Short
|
|
|
|
Guest
|
YAFPro Theme Created by Jaben Cargman (Tiny Gecko)Powered by YAF 1.9.3 |
YAF © 2003-2009, Yet Another Forum.NETThis page was generated in 0.105 seconds.