Are you trying to say that XAML isn't a declarative languageI think you misunderstand what a "declarative language" actually is.Because MSDN would disagree with you. Or have I missed your point there?
Hey! Potato salad was the best kick starter evah and I'll fight any man who says otherwisethere have certainly been worse crowdfunded projects...
edit> BTW I'm with Niya on the whole, C# and .Net being interchangeable thing. It's not to do with the ease of converting the code, it's to do with the fact that you needn't even bother. They're essentially the same language operating in the same environment. Indeed, I'm always quite surprised that MS haven't introduced compiler directives that would allow you to switch freely back and forth between the two as you code (although that might lead to some pretty horrendous looking code). That said, I also agree that it's kinda off topic where VB6 is concerned.
I think a more interesting question would be "What are the five killer features you'd like to see added to VB6 that aren't supported already?". Olaf's pretty much given his answer in post 548 but I'd be curious to hear what the other people want.Well, I've simply answered szlamanys question 1).




Because 
Reply With Quote