Script cache hashing

[Jeff]

VB has its niche. VB.NET has actually proved terrific at keeping VB relevant for all these years.

Sure, but that is only cause so many ppl learned VB before .Net came out.

 

[Suil Ban]

And VB was a terrific advancement for RAD back in its heyday.

 

[Jeff]

And VB was a terrific advancement for RAD back in its heyday.

Ya, but we need to move on from the cart and buggy

 

[shrundowr]

FORTRAN Forever.

 

[Murzin]

COBOL bitches... it will make its comeback.

 

[Lord_Greywolf]

assembly - the only true native language - with out it, there are no others

 

[MarciXs]

The only downside to vb script is the C# scripts cant reference anything made in them due to the compilation order.

or if you add this if( File.Exists( "Scripts/Output/Scripts.VB.dll" ) ) (for c#) or if( File.Exists( "Scripts/Output/Scripts.CS.dll" ) ) for VB.

and then m_AdditionalReferences.Add("the path to it");

inside the both c# and vb compiling methods.

Which would do the trick.

 

[Vorspire]

http://www.lolcode.com FTW.

 

[Jeff]

or if you add this if( File.Exists( "Scripts/Output/Scripts.VB.dll" ) ) (for c#) or if( File.Exists( "Scripts/Output/Scripts.CS.dll" ) ) for VB.

and then m_AdditionalReferences.Add("the path to it");

inside the both c# and vb compiling methods.

Which would do the trick.

Won't work since the VB compiles 2nd. C# compiles first and doesnt know about the VB classes..