npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gulp-aspnet-viewnames

v0.3.1

Published

Generates a c# file containing strong typed information about mvc views

Downloads

2

Readme

gulp-aspnet-viewnames

Travis npm npm License

Generates a c# file containing strong typed information about mvc views.

It also watches changes in the Views directory so that the file is always regenerated when necessery.

Install

npm install gulp-aspnet-viewnames --dev

Here is the npm package.

TL;DR version

Instead of this:

return View("~/Views/Home/Index.cshtml");

You'll be able to write this:

return View(Views.Home.Index.FullName);

Usage

This should be integrated into the gulp build process:

var viewnames = require("gulp-aspnet-viewnames");
gulp.task("viewnames", function () {
	return viewnames({
		ns: "TheNameSpaceOfTheGeneratedFile"
	});
});

Typically, you'll want to bind this to the Project Open binding so that the generated file is always up to date while you're working.

What happens

Run the viewnames task from within Task Runner Explorer. You should run it once (if you don't want to use the bindings), after that, it will continue watching over the Views and regenerate the file without your intervention.

Suppose we have the following directory under Views:

- Home
	- Index.cshtml
- Shared
	- _Layout.cshtml
	- Error.cshtml
- _ViewStart.cshtml

The following c# file will be generated (default name is ViewNames.cs):

namespace TheNameSpaceOfTheGeneratedFile
{
	// ViewName class skipped for brevity.
	// ViewName will contain a Name and a FullName property.

    public static class Views
    {
        public static readonly ViewName _ViewStart = new ViewName("_ViewStart", "~/Views/_ViewStart.cshtml");
        public static class Home
        {
            public static readonly ViewName Index = new ViewName("Index", "~/Views/Home/Index.cshtml");
        }
        public static class Shared
        {
            public static readonly ViewName Error = new ViewName("Error", "~/Views/Shared/Error.cshtml");
            public static readonly ViewName _Layout = new ViewName("_Layout", "~/Views/Shared/_Layout.cshtml");
        }
    }
}

So now, you can reference your views with strong typed values rather than hard coded ones, which are prone to refactoring issues.

The generated file should be ignored by your source control.