I am in desperate need of converting the Prefetch template used in the manager template to VB.NET, so if anyone could please help me, I would greatly appreciate it. I've tried a few different times and I just dont know enough about C#. I also tried running it through some converters, but it just isn't working. The place I am working at requires we use vb.net and the only template I can't convert is the prefetch one. Can someone throw me a bone?

I don't see any construct in there what would cause any problem with what converter whatsoever, could you give an example of what you can't convert?

IFoo[] bar = bla();

means: an array of IFoo's called bar.

The only thing you'll get problems with are the in-method regions. VB.NET can't handle these.

I used the following converter:

http://www.developerfusion.com/utilities/convertcsharptovb.aspx

Could you try and past in the code to this link? I think it may be easier to list this way. Also, it's only the class that is can't handle, not the other three interfaces.

Thanks!

Kristian wrote:

I used the following converter:

http://www.developerfusion.com/utilities/convertcsharptovb.aspx

Could you try and past in the code to this link? I think it may be easier to list this way. Also, it's only the class that is can't handle, not the other three interfaces.

Thanks!

I could do that, but if you could paste here the constructs you can't convert, that would save me a lot of time, as I don't know with which construct you have problems with.

Otis wrote:

Kristian wrote:

I used the following converter:

http://www.developerfusion.com/utilities/convertcsharptovb.aspx

Could you try and past in the code to this link? I think it may be easier to list this way. Also, it's only the class that is can't handle, not the other three interfaces.

Thanks!

I could do that, but if you could paste here the constructs you can't convert, that would save me a lot of time, as I don't know with which construct you have problems with.

I think the biggest issue is that the class implements three interfaces and it gets all confused. When I get home tonight, I'll go through and pull out the ones it has problems with. Thanks Frans!

Yeah that's a bit of a problem with VB.NET: in C# you just specify you implement an interface and the compiler figures it out. In VB.NET, they thought it would be nice to do some extra nagging by adding the requirement to specify which interface method you actually implement (which is totally irrelevant for the CLR)

So when you port the code, you should take the actual interface definitions and add the proper specifications (Implements IFoo.Bar) , and that's about it I think