This seems like a very basic feature to me. I can't seem to set C# as the default programming language for Visual Web Developer 2008 Express Edition. I've searched and searched and found nothing useful. Any ideas?
The reason why MVC is tagged is because it auto generates controllers and all that jazz -- in the wrong language.
When you create a new project, the 'Project types' panel on the left should list 'Visual Basic' and 'Visual C#'. Select a project from the 'Visual C#' list.
When you create a new website there should be a 'Language' drop down at the bottom left of the dialog to select 'Visual C#'
If these options are not available to you then I would guess that C# wasn't installed when you installed VWD 2008 Express
Related
I'm working on a few Umbraco projects that use MVC4. The MVC intellisense doesn't work within visual studio and I get lots of errors underlined. But when I run build the project, I don't get any errors, and when I run the site everything works fine.
I'm using Visual Studio 2013 and I created a new MVC4 site and compared the web.configs within the Views folder and they're identical.
I'm pretty sure it's not a code problem as my colleague is using the same code and he doesn't have this problem.
I've just done a fresh install of Visual Studio 2013.
Any ideas?
This could be a clue:
When I hover over #Htmlit tells me that my HtmlHelper is a System.Web.WebPages.Html.HtmlHelper instead of a System.Web.Mvc.HtmlHelper
The common one is to ensure that it is switched on (Visual Studio menu: Tools > Options > Text Editor > All Languages (or C# if you want it just for that language) > Tick "Auto list members", Untick "Hid advanced members", tick "Parameter information")
Once you've checked this, sometimes if you're using one HDD on Windows, because the disk has its bandwidth used up (particularly if using ReSharper then you need two or more drives ideally with the pagefile going to the non-OS drive I find). This is the case if the red lines do disappear after up to two minutes of not touching the IDE.
Finally check you project's references folder to make sure where the paths for your includes are coming from and that Visual Studio has permission to read from there. Permission issues cause all manner of problems I find, so when you launch VS, right click and choose "run as Administrator".
Hopefully one of these solves your problems. If not, then please update your question to explain how you create your project. Do you create an empty site or an MVC site? Do you then use Nuget to install Umbraco through the Package Manager Console like this?
Install-Package UmbracoCms
I was trying to use IIS Express in developing my first ASP.NET MVC.
I searched on the web and found out that I need to check a box in
Tools > Options > Projects And Solutions > Web Projects
The only items under the Projects and Solution node are
General, Build and Run and VB Defaults
Sorry, just a newbie in the field of web development
Thanks
Just to verify, I opened up my version of 2010 Ultimate and everything was there. I would suggest verifying that you have the latest version of MVC installed and IISExpress. This is all that I could think of that would cause it to be missing from the options menu(s).
I'm trying to open MVC project using VS2010.
I'm opening this project from TFS server but I'm failed to open it
and getting error :
The project type is not supported by this installation.
please help.
You basically don't have something installed. That's why you get this error. I am very sure that you need to install the VS MVC project type - either MVC 2 or MVC 3. Use The Web Plaform Installer to install. The web platform installer can be found here: http://www.microsoft.com/web/downloads/platform.aspx. Once you have installed it (it is only 2MB) you need to search for "MVC", install the MVC 2 and MVC 3 project templates.
I got this error when I forgot to select the Web Developer feature in the Visual Studio setup. Unfortunately, the error you mentioned is the only error you get when Visual Studio 2010 is installed without this feature. You can install the Web Developer feature using the Windows control panel.
By popular demand (7+ and counting), I'm placing part of CodingWithSpike's comment here. Specifically, the procedure to explicitly add Visual Web Designer to VS install.
open Control Panel
select Programs and Features (or Add/Remove Programs)
choose Visual Studio
click "Uninstall/Change"
this opens the VS installer in maintenance mode.
Click "Next" once
Click "Add or Remove Features"
Checkbox "Visual Web Designer"
click Update button.
Enjoy having a working product!
Edit the project.csproj file and look at the <ProjectTypeGuids>{E53F8FEA-EAE0-44A6-8774-FFD645390401};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
The GUIDS above includes MVC 3 Tools Update. That's a good guess of what you are missing. You can get MVC 3/TU from http://www.asp.net/mvc/mvc3
BTW, that install includes VS2010 SP1 which is required for the TU edition.
If you've installed Visual Studio 2010 after Visual Studio Web Dev Express and MVC4, Visual Studio 2010 doesn't seem to pick up the MVC 4 templates. Running the MVC 4 installer again via the Web Platform Installer doesn't fix it. Repairing the MVC 4 installation fixed it in my case:
Under Control Panel, choose Programs/Uninstall a program.
Find Microsoft ASP.NET MVC 4 and double-click it.
The Microsoft ASP.NET MVC 4 Setup prompt will appear. Choose Repair.
Visual Studio 2010 Express to Pro, ASP.NET MVC 4 installed but not an option?
in my case, i had opened my VS2010 solution, in vs2012, i was getting the project type is not supported, tried re installing mvc3 as was suggested, cancelled re installation, then i had the issue i couldn't open the project in VS2010 anymore. then tried to re install mcv3 again. solution was, uninstall mcv3, uninstall mcv4, then reinstall mcv3, then i could reopen my project in VS2010 . hope this helps someone!
I'm working through the Nerd Dinner ASP.NET MVC tutorial and am at the part right after I've created the project and am trying to run my unit tests for the first time. I see the test project and the AccountControllerTest.cs and HomeControllerTest.cs files that were generated but when I click on Test -> Run all options are greyed out. When I try the keyboard shortcut for tests I get a message that that key combination is bound to command (RunTestsInCurrentContext) which is not currently available. I'm running VS 2008 Development Edition.
Dont think they are available in VS 2008 Development Edition, you need Professional Edition
Look at Code Quality Tools section in the pdf on this link - Visual Studio 2008 Product Comparison Guide
Do you have the Express Edition? IF so the tests are not supported
I have the standard edition and built in tests are not supported so I use Nunit.
http://nunit.com/index.php
What is "missing" in the Visual Studio 2008 Express Editions?
In particular,
what functionality is not available?
what restrictions are there on its use?
The major areas where Visual Studio Express lacks features compared to Visual Studio Professional:
No add-ins/macros
Some Win32 tools missing
No Team Explorer support
Limited refactoring support
Debugging is much more limited (particularly problematic for server development is no remote debugging)
Lack of support for setup projects
No report creation tools
No Office development support
No mobile platform support
Limited set of designers
Limited set of database tools
No code profiling or test framework support
No MFC/ATL support
No support for compiling C++ to 64-bit images (workaround is to install Windows SDK which is free)
NOTE: it is often said that the Express EULA does not permit commercial development - that is not true (Visual Studio Express FAQ Item 7)
There's a handy set of comparison charts on microsoft.com.
It depends on the particular express edition, of course (since there are several and they have different features). The limitations you're most likely to run into are source control integration (and TFS client license), debugging limitations, limited refactorings, no unit testing support, and limited designer support.
For completeness sake, here's a list of features that are in Visual Studio 2008 Standard Edition but are in none of the express editions:
Add-Ins
Macros and Macros IDE
Visual Studio Add-in project template
VSPackages
Wizards
ATL/MFC Trace Tool
Create GUID
Dotfuscator Community Edition
Error Lookup
Source Control Integration
Spy++
Team Explorer Integration
Team Foundation Server Client Access License
Visual Studio 2008 Image Library
Add-Ins/Macro Security options
Visual Studio Settings
Class Designer
Encapsulate Field Refactoring
Extract Interface Refactoring
Promote Local Variable to Parameter Refactoring
Remove Parameters Refactoring
Reorder Parameters Refactoring
Debugging Dumps
JIT Debugging
Mini-dumps
Multithreaded/Multiprocess Debugging
NTSD Command Support
Step-Into Web Services Debugging
CAB Project Project Template
Merge Module Project Template
Publish Web Site Utility
Setup Project Template
Setup Wizard Project Template
Smart Device CAB Project Template
Web Setup Project Template
Windows Installer Deployment
64-bit Visual C++ Tools
Create XSD Schema from an XML Document
Reports Application Project Template
Visual Studio Report Designer
Visual Studio Report Wizard
Shared Add-in Project Template
ASP.NET AJAX Server Control Extender Project Template
ASP.NET AJAX Server Control Project Template
ASP.NET Reports Web Site project template
ASP.NET Server Control Project Template
ASP.NET Web Application Project Template
Generate Local Resources
WCF Service Host
WCF Service Library Project Template
WF Activity Designer
Custom Wizard Project Template
WF Empty Workflow Project Template
MFC ActiveX Control Project Template
MFC Application Project Template
MFC DLL Project Template
WF Sequential Workflow Console Application Project Template
WF Sequential Workflow Library Project Template
WF Sequential Workflow Service Library Project Template
WF State Machine Workflow Library Project Template
WF State Machine Workflow Designer
WF State Machine Workflow Service Library Project Template
WCF Syndication Service Library Project Template
Visual Studio Extensions for Windows Workflow Foundation Designer
Windows Forms Control Library Project Template
Windows Service Project Template
WF Workflow Activity Library Project Template
WPF Custom Control Library Project Template
WPF User Control Library Project Template
ASP.NET Server Control Item Template
COM Class Item Template
Configuration File Item Template
Frameset Item Template
Interface Item Template
CLR Installer Class Item Template
Local Database Cache Item Template
Module-Definition File Item Template
Nested Master Page Item Template
ATL Registration Script Item Template
MS Report Item Template
Report Wizard Item Template
.NET Resources File Item Template
Win32 Resource File Item Template
Static Discovery File (Web Services) Item Template
Transactional Component Item Template
Web Content Form Item Template
Windows Script Host Item Template
Windows Services Item Template
XML Schema Item Template
Here's comparison chart of editions
Edit: didn't realize this was for 2005, not 2008
Visual Studio 2008 Product Comparison
As far as I know there are no restrictions on its use, but I'm not a lawyer.
AviewAnew pointed out you can use Express Editions for commercial use: there are no licensing restrictions for applications built using Visual Studio Express Editions. See FAQ #7.
These are the most significant for me:
You cannot set breakpoints with a condition
Add-in support
Refactoring is very limited (rename, extract method)
MFC is the most important missing thing in my opinion.
No add-ins allowed
Other people have posted huge lists, but as a practical matter, speaking as someone who does mostly systems programming, the features I miss most when using the express edition are
the thread-aware parts of the debugger,and
the ability to open files with the built-in binary viewer.
If I did MFC programming more often I would probably miss the dialog designer as well.
One that is missing (which is nice to have) is:
Source Control Integration
enables two
options: source control solution based
on the Source Control Plug-in API
(formerly known as the MSSCCI API), or
a source control VSPackage
This is particularly important especially if you're working with systems like Perforce where you must check out files before changing with them, particularly changing project settings for all team members.
This MSDN document should get you everything you need!
Note that currently, you can't get F# in an Express edition, though I imagine that this is likely to change at some point in time.
There is a workaround - you install the Visual Studio Shell and F# CTP separately and they work together.
I had trouble with Visual Studio Express (C++) 2008 (with service pack 1) on Windows Vista, with debugging. Any time I did anything such as (a) break the program, (b) set focus from the app back to the IDE, (c) resume execution, the program hung for about 30 seconds. Task Manager showed "VSExpress.exe" consuming an entire CPU for the duration. Vista showed "Not responding" in the IDE's title bar during this time.
This was driving me bonkers so I bought a commercial copy of Visual Studio Professional 2008 ($150 from SoftwareSurplus) and this solved the problem.
For Visual Studio 2008, the Express editions do not have the built-in testing features for one.
You can build MFC applications if you download the libraries in the Platform SDK. But there is no built in support for designing dialogs.
Add-ins are allowed in Visual Studio Express. The most notable one is straight from Microsoft: XNA Game Studio works as a Visual Studio Express add-in.
There's even a project type (maybe only available in the full Visual Studio) that lets you build your own Visual Studio Express add-ins!
You can't create Windows services for one.