I'm arguing with one guy about linq in visual basic.He shows linq expressions in vb,but I can't be sure if it's managed or unmanaged(vb6),because I've never used any of them.
Does VB6 have linq expressions?
Visual Basic 6 does not have LINQ extensions.
VB6 is not related to VB.NET. It's a different language and platform. The two are related in the sense that C and C++ are related.
In particular, VB6 is not an unmanaged form of VB.NET.
LINQ is part of the .NET Framework. VB6 was released in 1998. .NET was released in 2002.
The VB6 IDE is unsupported.
Linq is fairly new (Released 2007). Its not supported by VB6 which was released about 1998
With version 7 Visual Basic took the step into .NET with managed code and real object orientation, leaving the old unmanaged platform behind. (Well, it was never called unmanaged, as there was no managed code...) Version 9 was released a while a go including LINQ support.
So, no VB 6 doesn't support LINQ.
The only way that you can use LINQ and Lambda expressions in VB 6 is to use COM Interop. The performance is still Okay regardless of the time that you need to consider for proxy and translators.
For scenarios that you need to use LINQ and Parallel LINQ(PLINQ) in your VB 6 code, the best solution is to use COM Callable Wrapper(CCW). To learn more, you can read how to expose a .NET COM to a COM client such as VB 6.
Related
I just started to study Nemerle. Since this is .NET language, I wonder, is possible to use for Windows Phone development? Does Visual Studio support it well?
Nemerle compiler uses System.Reflection.Emit for assembly manipulations. Then it can create assemblies same CLR version only.
I know only one reciepe for build WP assemblies: ildasm ncc.exe, fix all references to WP framework and ilasm it again.
This may not be possible, since Windows Phone runs a subset of the full .NET Framework which is closer to the .NET Compact Framework.
Looking at this page (translated from Russian) it looks like Compact Framework support is something that is/was planned for Nemerle version 2. However that article was written before Jetbrains acquired the project, so objectives may have changed.
Having said that, much more recently (Feb 2013) one of the Nemerle developers spoke about their difficulties in getting Nemerle to support other frameworks. So perhaps it is on their agenda after all.
I have never programmed VB, but a university course forcibly requires me to use it. Now, I've done VC++/Win32 programming before, but not the CLR(.NET). There's this free IDE from Microsoft, Visual Basic.NET express, that I plan to learn on. Is that okay? I mean I'm not learning .NET stuff, it'll be plain old Win32 with VB. Is that possible on that IDE? Will it require(read: force) me to use the .NET libraries instead? If yes, is there a free copy of VB 6 (or anything NOT NET) IDE still available? Excuse me if this sound noobish, but I really haven't ever touched on VB or .nET development.
If you have never learned old Win32 with VB aka VB6, I would advise you to skip it altogether and learn VB.net unless your end goal is to maintain legacy applications.
The concepts and libraries that you learn as part of VB.net will be transferable to C# which seems to be the most popular .NET language at the moment
VB.NET and "regular" VB are vastly different. VB6 was the last release of VB6 that is not managed. I question the value of learning this though. VB6 is unsupported, products for it are unsupported, and there isn't much you can gain by learning it instead of learning something else like VB.NET. If you really are stuck learning plain VB (which hasn't had an update since 1998), then you'll have a hard time finding resources.
VB.NET really means "A VB-like syntax language for .NET". Since the Express edition is for VB.NET, you cannot use it for VB development.
Your best bet is to find a copy of Visual Studio 6 or Visual Basic 6 Professional. You can still purchase them from places like Amazon.
MSDN Downloads has VB6 as well. You should contact your school to see if they can provide any additional resources. Perhaps your school can get you an Academic MSDN license (though I am not sure if that would include VB6).
You can forget about running those IDEs on Windows Vista or Windows 7. You'll need a copy of XP / 2000 as well.
I'd rather use the free Visual Basic 2008/2010 Express edition.
Is there an Online version of LINQ Pad?
There are two online services that I know of, which don't have the nice graphical features of LINQPad, but can be used as web-based C# (or VB.NET) scratch pads. I use them for testing the code in my StackOverflow answers on PCs without Visual Studio.
Ideone
http://ideone.com/
It uses mono 2.8 and, thus, supports LINQ to objects. Apart from C# and VB.NET, Ideone supports a variety of other languages.
DotNetFiddle
https://dotnetfiddle.net/
DotNetFiddle lets you choose between .NET 4.5 and Roslyn and supports NuGet packages.
What is the need to use delphi prism instead of Visual studio;
i am a delphi programmer so i like object pascal but what else are that delphi prism have that other does not have
What do you mean by "Delphi Prism instead of Visual Studio"?! Delphi Prism is a pascal-flavor in .NET platform. Visual Studio is an IDE. Delphi Prism uses Visual Studio as its IDE. So when you code in Delphi Prism or debug your prism codes, you are doing it in Visual Studio, just as doing with C# or VB.NET.
.NET is supposed to support multiple programming languages and providing common types and libraries to all languages targeting it. Delphi Prism is just another .NET language. It has access to all the stuff that .NET provides to languages. It also has some distinct language features (refer to PRUZ post).
So you can use Delphi Prism when you want to code in Pascal for .NET platform, or if you really need any of its distinct language features in your .NET applications.
Of course Microsoft's own languages (C#, VB.NET, F#) have little edge in .NET over third-party language providers:
There are so many books and articles - including MSDN -
written about MS languages, or written about .NET with C# or VB.NET sample codes (recently Delphi
Prism added a tool to automatically
convert C# code snippet to Delphi
Prism code).
New .NET features would be
available first to Microsoft's own
languages first, and then to other
languages, so if you need a really
new .NET feature, you might have to
wait a few months to have it in your
favorite language.
And, some IDE features like visual
form designer for .NET compact
edition are only provided for C#
and VB.NET.
Like any other programming language, we don't need Delphi Prism. But Prism is an option for software developers with a Pascal/Delphi background to start developing for DotNET. Is this important? For some, yes. For others, not really.I have over 20 years of experience with Pascal and am familiar with every Delphi version since the first one. But 8 years ago, I also learned C# simply because Delphi was too weak as a tool for developing DotNET applications. And unfortunately, no matter how much Embarcadero/Borland tries, their development of Prism will also be behind the generic DotNET products that Microsoft keeps publishing.The advantage of Prism is that it's an add-on for Visual Studio. And you can use Prism to write applications for the Mono platform, which is used on Apple's Mac computers. It can also work together with C# and VB.NET applications and you can create mixed projects where you use Delphi, C# and VB.NET to create a single product. (Made of multiple assemblies, though.) Prism allows you to create Pascal code that you can use in your regular WIN32 environment but also in DotNET. This code can't be too platform-specific but in general you can get some very good results this way.Delphi Prism isn't fully developed by Borland/Embarcadero, though! It started with RemObjects, who created an alternative compiler for Delphi-like code, but with some additional features that you won't find in regular Delphi code. RemObjects started to just push out Delphi for DotNET from the market, since RemObjects provided a nicer product and they had focused more on the DotNET issues. So the two started to work together to create Prism.Like any programming language, Prism has some features that you won't find elsewhere. If those features are practical always depends on if you can find some practical usage for them. In my personal opinion, if you already have Visual Studio and you're only creating applications for the Windows platform then you won't really need Prism. If you have additional Delphi experience, you might like Prism for some projects. If you need to port a Delphi/WIN32 application to DotNET then Prism might help with that. But I don't know of any advantage that would make Prism a requirement.
Personally I think Delphi Prism do more bad than good for the (real) Delphi ecosystem.
I can not deny that the RemObject's product has many interesting things and technically well done, but as a (real) Delphi programmer and enthusiast I see that thay are dangerously distracting the attention and giving some ambiguos non clear message to new comers and .Net programmers.
A (MS) .Net programmer will never move to D. Prism, only Delphi programmers who wants a smooth transition while leaving the boat.
Since there is no tie between D. Prism and (real) Delphi it was a bad move to name it Delphi. They share some basic pascal syntaxis but that's all. They even do not share their improvments, nor they can be used fully integrated.
I bought Rad Studio for Delphi and C++ but I spend most of my time with Prism. As for the old saw that third party products for net are behind the Microsoft products, I say that is just ignorance talking in this case. Prism is not lacking anything that C octothorpe or Visual Basic has. The net system is best programmed by Hejilsburgs' best language, object pascal, and Rem Objects has been improving the best language for net all the time. Those guys at Rem Objects move fast and make things happen. All the updates come from them, Embarcadero just stands and salutes. By the way, the C# to Prism convertor really works. I grab code at msdn and paste it into Prism with no worries.
You can view old question Will you use Delphi Prism, about many opining about Delphi prism from Delphi developers and others.
Is it worth spending time in these frameworks. Or they just another framework like microsoft developed in the form of MFC library.
I dont want to waste precious time, so please help. Under what scenarios these frameworks will be helpful.
EF and L2S are Object-Relational Mappers (ORM). They would be used wherever an ORM is used. StackOverflow uses Linq to SQL as its ORM layer, to good effect. Entity Framework is up-and-coming, and although it currently has issues, it will be greatly improved in the upcoming version 4.0.
Your time would be well spent learning one or both of these frameworks, as it will be highly likely you will use an ORM in your applications at some point.
It really depends on what your alternative is. If your alternative is using ADO.NET and DataSets, then yes, LinqToSql and EntityFramework are likely a step forward. If your alternative is NHibernate or another feature rich ORM, then they may be a step backward.
Microsoft has really strongly moved away from LinqToSql while still continuing to offer support for it and making minor changes. Microsoft is recommending all LinqToSql users move to Entity Framework. However, the Entity Framework that came out with VS 2008 SP1 / .NET 3.5 SP1 was in many ways a step back from LinqToSql. The Entity Framework that is coming out in April with VS 2010 and .NET 4.0 should be mostly an upgrade from LinqToSql, assuming you can migrate to VS 2010 / .NET 4.0 sometime in the near future.
YES! It is worth Learning. No! its not just another framework. It is useful for any application that uses a SQL Database to query data and present/do some logic.
Linq2Sql was introduced with .NET 3.5. Very useful if you dont have your own set of domain entities. A bit difficult to map Linq2Sql classes to our own domain entity classes in complexed scenarios.
But, recommend to use Entity Framework. EF was introduced with .NET 3.5 SP1. Much improved version of Linq2Sql and came as part of Olso Mixed Models. This can be used as a real ORM to map our own set of domain entities and the designer provides most of the features.
There is a new version of EF (EF4) ships with .NET 4.0.
Watch Evolving ADO.NET Entity Framework in .NET 4 and Beyond for what you can do with EF4.
Download the "Layered Architecture Sample for .NET" from Codeplex.com