I have installed VS2013 installed on my computer. I also installed
Visual Studio 2013 Update 2 RC
and
Web Essentials 2013 for Update 2 RC
successfully. Now when I work on a website project, go to WEBESSENTIALS top menu, and select create solution settings, I get the following error message:
Path cannot be null.
Parameter name: path
Does anyone know how to solve this issue?
Also, I want use the LESS feature of web essentials. Can anybody tell me how?
Thanks!
You may need to add a solution to your project to create a Web Essentials solution settings file. If your project (Web Site) doesn't have a solution, I'm guessing there's no solution to apply settings to.
What I do is create a New Empty Project, then add a New Web Site... or Existing Web Site.. to the solution.
It seems in my experiences that when I use 'File > Open Website', it creates a temporary solution, but Web Essentials doesn't seem to use this for its solutions settings.
Right-click on the targeted project in your solution & "set as startup project."
Related
I'm using Visual Studio 2015 Enterprise RTM.
When creating an ASP.net 4.6 web application using the Web Api template, I noticed as soon as I add a TypeScript file, the codelens indicators stop working.
I tested this on a new installation, with no extra extensions installed, as well and tried other asp.net 4.6 templates.
When running in safe mode the problem doesn't occur.
Steps to reproduce:
Set the framework to 4.6
Create a web application by using the web api template.
Change authentication to no authentication
Open the webapiconfig.cs in App_Start
The codelens indicator on the register method should say: 1 reference
Add a typescript file called app.ts (doesn't really matter) in the scripts folder, tit may remain empty
The codelens indicator in the webapiconfig file should still say 1 reference
Close Visual Studio
Reopen Visual Studio and open the solution
Check the webapiconfig file, the codelens doesn't show references anymore or on any other file
Any idea on how to debug codelens or does anyone have this problem as well?
I work for the visual studio team that is responsible for codelens references indicators. I can confirm that this is indeed a bug in VS2015 where codelens references stop working when you add typescript files to your project or typescript projects to your solution :( Unfortunately, we missed this bug for RTM. We're currently actively investigating this bug. At the moment, I am not aware of any workarounds for this problem. I can post an update when we have more information to share on this bug.
I may have found a workaround that seems to do the trick for me:
So, I have a solution with multiple projects, only one of which has TypeScript files.
I just unloaded the project, cleaned + rebuilt (some restart to Visual Studio at this point may help + close all opened files), then loaded again, cleaned and rebuilt and now CodeLens shows my references (again, close all open files).
Note that until this bug is fixed, you may have to do this each time you open VS.
Hope this helps!
EDIT: If you only have a single project, then exclude the Scripts folder from the solution, clean, rebuilt, close Visual Studio then open it again. Now you should have the references back. Simply include the folder again.
Best of luck!
in my case references start working after uninstalling vssonar extension, vs2015ent
When I try to open a class diagram for my asp.net webforms project I get the following error. The Class Diagram (.cd) files get generated but I can't open them.
I do have some classes that use the URI class but i don't really think that could be the issue. Right? Why would a class diagram care about one of my classes using a URI datatype?
I'm using vb.net Visual Studio 2012 and the project is targeting .net 4.0. I'm aware there is another question in stack overflow asked about the same issue, however there were no answers posted to it and it's close to a year old.
Help will be greatly appreciated, thank you.
I had the same problem and was able to fix it in Visual Studio 2012 Professional just now for a website I am working on with my team.
This is not about one of your classes using the URI data type.
My setting under "WEBSITE" in Visual Studio was previously set to "Use IIS Express". When it is set this way, you can select the alternative option, again under "WEBSITE" which is "Use Visual Studio Development Server". I'm not certain, but I think this is what the other posters describe above when they say "open web site in file system mode". When I am not using IIS Express, the class diagram generates, is not blank, and opens fine for viewing in the IDE.
Please open web site in file system mode (and not in IIS express ) and it will work.
when you load the website, visual studio will tell you that it is already using IIS Express to serve websites do you want to continue using it or not, select no so that you can use visual studio and bot the IIS. my things worked after that
I created an Empty Website (not a project) using File > New Website > Aps.net Empty Web Site. Usually when I click on Build, there is an option to "Publish Web Site". However, I don't see it here. All I can see is build and rebuild solution. What am I doing wrong? Even when I right click on the website, it just gives me an option to Build, but not Publish. I previously was using VS 2010, and it has the Publish option.
Publishing is only support for web application projects, not web site projects.
http://msdn.microsoft.com/en-us/library/dd547590.aspx
I don't know if this is true in all cases, but I just uninstalled VS 2012 Web Express, deleted the contents in the Microsoft Visual Studio 11 folder, and then installed the Professional version instead. Maybe the Express version doesn't have this, but after installing the Professional version, I do have the "Publish Web Site" option.
I believe this problem can be solved by downloading and installing the relevant Web Publish Update from this web page:
http://msdn.microsoft.com/library/jj161045
I had the same problem in Visual Web Developer 2010 Express. When I installed the update, the option to "Publish Web Site" became available to me.
EDIT: You may find that when you click "Publish Web Site", you get an error like this:
the imported project "C:\ProgramFiles\MSBuild\Microsoft\VisualStudio\v11.0\WebSites\microsoft.website.publishing.
targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I solved this problem by going into "website.publishproj" (found in the Solution Explorer with my website open), and "hardwiring" the WebPublishTargetsVersion element like this:
<WebPublishTargetsVersion>10.5</WebPublishTargetsVersion>
For some reason, the existing code was returning 11.0, instead of 10.5.
Hardwiring it like this might cause problems later if you update your version. So do it with caution.
I'm new to ASP.NET and I'm learning first in WebMatrix using razor syntax.
In PHP I used .htaccess to route URLs to database posts, for example:
http://mywebsite.com/linux/how-to-install-wamp-in-ubuntu-12.04
In that case routes to file:
http://mywebsite.com/routes.php?title=how-to-install-wamp-in-ubuntu-12.04
I'm trying to route like the PHP example:
http://mywebsite.com/routes.cshtml?title=how-to-install-wamp-in-ubuntu-12.04
Can I do it in ASP.NET with WebMatrix and razor?
I know how I can take GET data in ASP.NET, but I don't understand how I can make a friendly URL and how I can route to "routes.cshtml" when the page isn't found.
There is an existing package specifically for ASP.NET Web Pages that lets you do what you want and it is available via the WebMatrix Package Manager. It is called Routing For Web Pages. I have written an article on how to use it: http://www.mikesdotnetting.com/Article/187/More-Flexible-Routing-For-ASP.NET-Web-Pages
Details: Microsoft is now making this very easy to do for ASP.NET Via a Nuget Package. Unfortunately, this package "Microsoft.AspNet.FriendlyUrls" is currently in Pre-Release and WebMatrix doesn't allow you to download Pre-Releases. As a result, following my way of doing it might not be as easy compared to if you just had Visual studio or VS Express.
My suggestion is to download Visual Studio Express 2012 and either use that for developing or just use it so you can get Nuget Packages.
Ill assume that you want to develop in WebMatrix.
Solution:
Download and Install Visual Studio Express 2012.
Create a new Website
In solution Explorer, right click on your Website and select "Manage Nuget Packages.."
Press the drop down that says "Stable Only" and choose "Include Prerelease"
In the search box enter "Microsoft.AspNet.FriendlyUrls"
Select "Install"
Open your project in Windows Explorer so you can see all the files.
Copy the folders "App_Code" and "bin" into your WebMatrix Project (e.g. Add them to your solution).
Add a Global Application Class "Global.asax"
In the Application_Start method add the following line
RouteConfig.RegisterRoutes(System.Web.Routing.RouteTable.Routes);
You will now have FriendlyURL's
I know this seems like a lot of work but if you had Visual Studio or WebMatrix allowed Pre-Released then it would be very easy to follow.
Warning: If you do decide to develop it in Visual studio delete the following files as the Mobile part of it doesn't work currently (Hence why it is Pre-Release)
Site.Mobile.Master
LiSite.Mobile.Master.designer.cs
ViewSwitcher.ascx
ViewSwitcher.ascx.designer.cs
Future: In the near future there will be release version of FriendlyUrl's and then you will be able to get it from Nuget in WebMatrix much more easier.
Links To More Information:
Information on Microsoft's Friendly Url Package
Information on how to use Nuget in WebMatrix
of course you can, it is called URL Rewriting
http://developer.mindtouch.com/en/kb/Installing_MindTouch_Core_on_Windows_%28IIS%29/Rewrite_web.config_for_IIS7
or here
http://www.phpgenious.com/2010/04/url-rewriting-with-php-and-iis-7/
or google for more info
I use the publish option of asp.net 2.0 to create a deployable copy of my web application. Lately I've noticed that the System.Web.Extensions.Design.dll and the System.Web.Extensions.dll does not get copied when using the publish option.
Has anyone any idea why this could have happened?
Couldn't google anything definite about this too...
Thanks.
They're part of the framework, so they are not published.
As others have pointed out they are part of the .NET framework and installed into the GAC which is why they aren't copied in a publish. Visual Studio expects them to be installed in the same location on the deployment target.
That said you can change this, right-click on the reference go to Properties and change the Copy Local to true. This will put a copy of the assembly in the local bin of the website and copy it when you publish.