Can I use LINQ within VS2005 if I have .NEt 3.5 installed?
The thing to remember is that at it's core Visual Studio, like any IDE, is a glorified text editor with an integrated debugger, and maybe a few other features as well. You could certainly use Visual Studio 2005 to input the code text of your linq program and then use the .Net 3.5 command line compiler to build it. You might even be able to find or write an add-in to automate the build process.
That means the technically correct answer to your question is, "Yes."
However, you won't get any extra IDE support:
Incorrect/broken intellisense.
Incorrect/broken syntax highlighting
Inability to work with .Net 3.5+ solution files.
No debugger support
The result is that you would probably be better served if I had simply said, "No."
If you already have 2005 but not 2008, you have a few options:
Get the 2008 Express Edition
Use a third-party tool like #Develop
Buy a 2008 full edition
There is no direct compiler support for LINQ in VS 2005.
You can still use the LINQ namespace and methods, however, it is not as elegant as using it in VS 2008.
See this article for details.
Vs2005 and C# do not directly support Extension Methods, Lambda Expression, Anonymous Types or Expression Trees which are key enabling features of LINQ. Some of the early LINQ betas did work with VS2005 and C# but none of the release products.
Likely the same for VB but I can't directly comment on VB other than I am about 99.99% sure you can't.
Simple answer is no.
LINQ relies on language features (such as extension methods) that VS2005 does not support.
Related
I'm using Visual C++ in Visual Studio 2010 Express, and in the past I remember when you use a string object and after the dot (eg: .) all the member functions will show in list, but that's not happening.
string myString = "hello world";
myString.
After typing the dot, all functions that are part of the string class don't show. Where in Visual C++ is the setting to make them show?
The functionality you refer to is called IntelliSense in Microsoft-speak, their version of autocompletion for variable names, functions, and methods.
IntelliSense is not supported in Visual Studio 2010 for C++/CLI projects. You will only get IntelliSense for projects written in native C++ code. This is explained in more detail here on the Visual C++ Team Blog. There is also a bug filed on Microsoft Connect; the official word is this:
Thanks for your feedback. Unfortunately in this release we had to cut the intellisense support for C++/CLI due to time constraints. If you want to get some intellisense like quick info and memberlist on the native classes you can get it by choosing no /clr support in the project properties.
Thank You!
Visual C++ Team
This is unfortunate news for many of us who work with C++/CLI projects, and we aren't left with many options. A question regarding those options has been asked here: What are people replacing the missing C++/CLI Intellisense in VS 2010 with? The summary is people are either going back to VS 2008
(I believe the Express Edition of 2008 is still available for download if you look around), or purchasing third-party software such as Visual Assist X that promises to bring back IntelliSense.
It's worth mentioning, however, that Microsoft does not regard C++/CLI as a "first-class" .NET language. There's little (if any) reason to start new projects using the language. It's designed for interop purposes between native C++ and managed C# applications. If you want to write C++, you should target the native Windows API (create a new Win32 project in VS). If you want to write managed .NET code, it is highly recommended that you use C# instead (that's a different version of Express that must be downloaded separately). The syntax is very similar between C++ and C#, but you will still have to learn the .NET Framework and idioms. Both native C++ projects and managed C# projects have very much improved IntelliSense support in Visual Studio 2010, so you're guaranteed to be much happier with either of those.
Are there gdb (or similar) for F#?
What tools/programs do F# programmers normally use for tracing F# code in Mono?
Does Visual Studio 2010 provides some integrated debugging tools for F#?
Visual Studio 2010 provides a fantastic debugging experience for F#, including breakpoints, tracepoints, call stacks, locals, stepping, set next statement, threads window, poking new values into variables, debugger visualizers, conditional breakpoints, immediate window, ... the only caveat is that the last two use the C# expression evaluator (F# does not have its own debugger EE), which means you must type e.g. C# syntax into the 'immediate window'.
(Everything I mentioned above is available for free if you download the free VS2010 Integrated Shell and the F# CTP.)
I am not sure what is available right now for Mono, but would not be surprised if there is something decent already, and something even better coming in the not-too-distant future.
Mono has its own debugger. The debugging format situation is slightly confusing because Visual Studio will generate pdb files which are needed for their debugger. Mono uses the alternative mdb format. fsc.exe (The f# compiler) will generate the appropriate ones for whichever platform it is run on.
The Monodevelop IDE can be used for general debugging of .net assemblies, even though it doesn't support a released f# version yet. You'll need to refer to your project's generated assemblies in the project.
Note that you also have to pass '--debug' to mono if you're executing it on the command line and want, for example, file names and line numbers in stack traces.
Any .NET debugger should work on F# code. The Visual Studio debugging experience is basically the same as for any other language (e.g. you can set breakpoints in the editor, etc.). I can't speak to what tools people use on Mono.
LinqPad understands F# code but I did not try it. A paid version gives you debugging.
I got started with F# back in the day (before VS2010 beta); at the time, if I remember correctly, there was not an Express version of F#, but one could use the VS Shell (I think that was the name) and then install F# on top of it.
What's the current state of affairs? I've read out there that there's no 2010 Express version of F#; is there a 2010 Shell that one can download and install F# latest on top of? If not, what's the best way (if any) to code in F# 2010 for free?
I'm aware that asking for free stuff is A LOT to ask for. But this was possible in VS2008 and I'm wondering if it's also possible in VS2010.
Thanks!
PS - I believe (not sure though) that VS2010 beta can be downloaded for free; the problem with that is that when the final release comes out, one will have to pay for a license. For a guy who codes for fun like myself it doesn't make much sense to buy the full version if I can get the very basic features for free...
See
https://stackoverflow.com/questions/734525/getting-started-with-f
Basically right now you can use the free VS2008 integrated shell along with the F# CTP, or use the VS2010RC (which is free as a Beta).
(I don't know if there is a VS2010 shell published yet, and I don't know if the F# CTP works with it; for the moment, your best long-term-free strategy is to use 2008.)
I think you can also use SharpDevelop with F#:
http://www.icsharpcode.net/OpenSource/SD/Features.aspx
If you mean visual F# the best tool is Visual Studio 2010 RC:
Check out these links :
Creating Your First F# Program with Visual Studio
Using Visual F# to Create, Debug, and Deploy an Application
**[Update]**Check out this link too:Features of the Visual Studio 2010 Release of Visual F#
Anybody know any plugin for Visual Studio 2008 that has the ability to "Structural Highlighting" and Syntax support for Delphi-Prism.
Currently use Castalia and CnPack, but just work on Rad Studio.
I've also used Codekana, but does not support the syntax of Delphi Prism.
Bye.
Given the comments, the answer probably is 'there is not yet structural syntax highlighting for Delphi Prism' :-)
You might also want to contact the people at DevExpress, or hook the people at DevExpress up with the people at RemObjects.
RemObjects is the company that developed the whole Delphi Prism language and Visual Studio IDE integration: that product is called Oxygene.
CodeRush does structural syntax highlighting (and much more, even in their free edition). It used to be available for Delphi, but is now Visual Studio only, and works for the C# and VB.NET personalities.
Mark Miller is the guy behind CodeRush (he started it in the Delphi world).
Since CodeRush is based on DxCore, DxCore does C#, VB.NET and ASPX, and DxCore is public, so you could roll your own structural syntax highlighting :-)
Julian Bucknall (CTO of DevExpress) already hinted on support for Delphi Prism in their products and elaborated on that.
Olaf Monien wrote about using DxCore to enable Sync Edit for Delphi Prism.
Personally I have not used Codekana yet, mainly because I rely on macros and refactoring a lot. At first sight Codekana does not support those, but I'd love to be corrected on that :-)
There is no product that provides structural highlighting with syntax support for Delphi Prism under VS.
Excellent question, which highlights an available development niche.
hmmm, it's not quite the same, but i use smartoutline in visual studio 2008. It's mainly for collapsing specified regions of code, but it also marks up the structures in the margin. You have to specify the regions yourself, but once done it makes code a lot easier to read
I have been using Visual Studio Express versions. I used to use the full Pro VS 2005. I can't figure out what I am missing with the Express version. What benefits will I get if I buy the full version of VS?
Here you go. This link is vs2005 specific rather than the more-recent 2008, but that's the version you asked about.
Some highlights:
No Mobile Device support
No Object Test Bench
No Extensions
No built-in source control support (they should really change this)
No remote debugging
No Office Development support
No 64-bit compiler support
No Visual Studio Package support
No profiler
No SQL Server debugging integration
Limited deployment options
This list is actually quite lengthy, but with the notable exception of source control they are mostly things you might be able to do without as a single developer, if you really have to. Even the source control can be handled by a file-system-only tool like Tortoise.
Obviously if you're building something like a smart phone app or VS extension it's a non-starter, so you'll need to evaluate what you're really doing. Some of the other missing features like object test bench or the profiler can be partially replaced by third-party tools.
Here's a link to a downloadable Visual Studio 2008 Product Comparison Guide from Microsoft.
The full version of Visual studio supports some extra features and tools.
One of the big differences is more debugging options (You can specify break conditions for debugging, unlike the express version). That feature alone is probably worth it.
You can also install 3rd party addons to add extra featues.
No Resharper.
also, you can add addins like VisualSVN and Resharper into pro. You can't into express.
Matze might be right - MS needs the money - 5K people layed off today, and only 4.7b profit! :(
Depends on what you do. Look at the product matrix to see what features you gain with higher SKUs. Testing, Smart Devices, etc may or may not be relevant for you.
This really just requires a bit of Googling.
You can view a comparison of the paid versions here and an overview of the Express versions here
Have a look at this:
http://blogshare.members.winisp.net/docs/VisualStudio2008-ProductComparison-v1.02-Revisions.xps
If you are doign any sort of professional development with Visual Studio you should buy the Standard edition at a bare minimum. Without it you will loose Source Control integration which IMHO is vital absolute must no questions asked must have for professional development.
I used VS2003 for a while, and am currently using VS2008 C# Express.
Personally, I miss the ability to set a conditional breakpoint instead of simply breaking when a line is hit, and the Threads window.
Support for code version systems is a feature that is real essential.
And Microsoft needs your money to go on implementing new, hot stuff.