I'm starting a new ASP.NET MVC 2 project, but unfortunately I'm a noob dev. Can you recommend a template I can use for my web site? It would be nice if the CSS supports stuff like 3 columns, 3 rows, with up, left, down and right parts being fixed size and the center auto sizing. Actually a clean CSS template would do too.
TIA
You can try freecsstemplates.org
They have some free CSS templates you can use to get started.
Your views in ASP.NET MVC should be primarily content and not structure. Same is true for ANY web development. As much of the structure and layout should move to CSS as possible. The reality is that you often have to compromise, but I'd start with CSS as much as possible.
Have you done much web design? If not I'd start there. Learn HTML and CSS first. Those apply whether you are doing ASP.NET MVC, Webforms, Ruby On Rails, PHP, or Perl + CGI (or just abut any other web dev) on the back end.
Related
I am trying to learn ASP.NET (C#) and the biggest struggle I am having is the design aspects of it. I have primarily been a windows form designer. All of the projects I have worked on have used windows forms and it was much more intuitive and cleaner to design in than HTML/CSS. I am trying to learn how to design web pages, but it seems all "design" needs to be done in CSS. How do you design something you don't see and just use pixels and references to other objects? I don't see how you design anything that way.
What is the best way for me to be able to effectively design for websites using CSS and ASP.NET coming from a more visual approach of windows forms? I have read 3 books on ASP.NET and it makes sense but all of the design is done is source views and CSS sheets. Is there another method or approach I should be aware of? I am using VS 2015 BTW as my IDE.
Please and thanks
CSS and HTML are the building blocks of the Web. Like you, I used to struggle moving from the Drag and Drop world of VS 2003 after initially starting out with just Netscape and Notepad in college. Drag and Drop, like Web Forms, is an unhealthy layer of abstraction in that it removes us from a true understanding of how the Web works.
Just accept that this is the nature of things and stop fighting it. Back in the days of VS 2003, our team would set up VS so as to never default to the designer panel when starting or opening projects. Besides, the tool was totally undependable and created a tangled Frontpage-style mess of so-called HTML.
Make the switch to pure, semantic markup and CSS. Download a good template from a site like Creative Market (I usually search using "Bootstrap 3") to learn from. Study HTML5, CSS3 and RWD (Responsive Web Design) and let yourself have some fun. Yes, it really CAN be fun.
Work by switching from your IDE to the browser and back again.
Hi I am developing a website with multiple pages. I am a beginner, coding is still a challenge for me, but my main hardship is designing my website. Visual studio is very not intuitive when it comes to designing websites, and sometimes you feel (when you try to design) like you work while tied in a straightjacket. I am used to dragging stuff around when designing, but this doesn't work with websites. There are a lot of website templates, but is there any which work with asp.net? And how do you integrate them while working in visual studio? Any help?
You don't need any special templates to work with ASP.Net. Integrating a template works the exact same way as it would if you are designing a site from scratch.
Find out your major pieces that are in every page (or groups of pages) and create your master pages that will provide consistent layout for those pages.
Forget about dragging and dropping and pixel design locations of a regular desktop app, it's not going to work that way.
Start with a framework such as Bootstrap, or a template based on Bootstrap. It's extremely well documented, works cross-platform, and there are plenty of tutorials out there on using it.
Visual Studio works pretty much like any other web design tool does. You're just running into exactly how things have been done for well over a decade now. Tools get better, but the web is an entirely different experience that requires entirely different ways of doing things.
You can easily templates or frameworks into your site. You can add styling to form fields, buttons, etc. easily through the CSS of the template.
Take a look at Bootstrap to get an idea of how you can style elements and understand the layout tricks that can be accomplished with responsive design.
So I am trying to change the CSS up in MVC 5 from the default bootstrap view that it renders. In some examples I have seen from MVC 4 which didn't use bootstrap by default I don't believe, it has a much better looking template in my opinion. MVC 5 has the plain black bar across the top, I know MVC 4 is also simple but I prefer that one. The only problem is I can't seem to find the source code, or the original CSS files they used for it anywhere? Every tutorial that I can find simply uses images instead of providing the files that I would need to add it to my project.
Here is the look I am going for...
http://i1.asp.net/media/45041/mvc4-restyled-templates.png?raw=true&cdn_id=2014-05-05-001
The default look that MVC 5 using bootstrap provides is..
http://eduardopires.net.br/wp-content/uploads/2013/07/aspnet_mvc5_build.jpg
Any suggestions on how I might switch to the previous version, or where I might find the proper CSS files to change it? I am trying to do this to an existing project so starting over really isn't an option. Thanks ahead of time.
You can install MVC4 side by side with MVC5 and create web project with MVC4 template. From there you can obtain the css you're looking
I have an asp.net website, it contains database calls etc
Whats the best way of taking an existing asp.net website and making it look good in mobile and tablet devices?
I have done some research but there seems to be so many options eg lessframework.com, jquerymobile etc
I havent used mvc before but a few people say to use mvc + jquerymobile
any help would be muchly appreciated
There is no magic bullet that will instantly convert your website to mobile. In fact without knowing the specifics of your website it would be hard to recommend a good fit for your situation since the tools you mention like MVC, JQMobile, etc. would be used in one case or another. With the question as you have posed it you will get personal opinion and there are millions of us with opinions... here's mine:
I would recommend not building a mobile specific website like mobile.website.com but rather look into responsive design where your website and the underlying data structs remain the same but your view changes depending on screen real-estate. Bootstrap or HTML5 Boilerplate or any number of design frameworks will help you get started. You just need to figure out a design that fits your websites functionality.
I use MVC + HTML5 Boilerplate (I love Razor) for most of my new projects but sometimes even it has too much overhead so I just start from scratch (multiple PSD's, convert to HTML in Dreamweaver, apply logic with MVC & client side scripting) but that is something you will have to decide on a project by project basis.
Past, now irrelevant back story: I was trying to make some changes to BlueBand and get 'up and running pretty quickly' but after looking at it further this is no longer an option due to tables that a previous developer introduced into the layout. I'll have to live with this and make what tweaks I can.
So, looking towards future greenfields projects...
Are there any recommendations for CSS frameworks that work nicely with SharePoint publishing sites? (Examples are BluePrint, YUI.) They should not interfere with standard out-of-the-box controls such as the Site Actions menu, rich text editor, and publishing toolbar.
Real world experiences welcomed, please!
What would you like to use a CSS framework for? As far as I can tell you could use one for making a cross-browser reset but everything else just depends on your layout. If you're planning to throw out the standard SharePoint layout it means that you need to start from scratch. The good news is that it's not much different than creating a layout for any other website. There are some things you need (http://msdn.microsoft.com/en-us/library/aa660698.aspx) while working with SharePoint but as for CSS it's all up to you.
Heather Solomon has a great blog/guide on wiring up SharePoint CSS classes - take a look:
http://www.heathersolomon.com/content/sp07cssreference.htm
Cheers,
Adam
You will run into a lot of trouble trying to hack the blue band theme into a table less layout.
You may get some mileage from the free Accesibility Kit for Sharepoint.
It comes with layout pages, CSS and even control adapters for those who care about the HTML of thier site.
Still, getting rid of the tables produced by SharePoint is not really compatible with "up and running pretty quickly"
You should start with the minimal masterpage. That will be the masterpage that's connected to the publishing layouts. You can then add in all the html/css you desire to your masterpage and layouts to make them look like anything you want.
If the users who are browsing those same publishing pages also need access to your list forms (new,edit,display) you will have to edit those files and attach them to your masterpage (either through SP Designer or a Feature to do it automatically). Or, customize the application masterpage to be nearly the same as your publishing masterpage and deploy them both as a feature with an HTTP Handler that changes the masterpage for the application.master at runtime.
Also an FYI, there are many issues once you start customizing list form pages for a site accessible to anon users, so do your research first on that one if needed.
We have used 960.gs with some success. Just include it in your master page, and wrap the main content area with a - or use container_12/container_24. Then in your individual page layouts, you can leverage all the columns/push/pull/alpha/omega goodies that make 960 so great. This works in 2007 and 2010, just takes a bit more work in 2007.
You can use any framework you desire when working with Sharepoint, however, the primary concern is how much control you have over web parts. OOB web parts use table based layout. If you have full control over how the web parts use the markup they product then you are one step closer to using a framework with little headache.
To alleviate some of the table based layout used in web parts you can look at accessibility toolkits to convert the web parts appropriately.