I am used to working with ASP web apps and creating .aspx pages. I don't know PHP really and I have worked a while with C# and ASP. I really like bootstrap so far and designing with it in HTML looks great and seems to work great. However, I am concerned that somehow this won't transfer over to ASP.
Twitter Bootstrap is just a bunch of CSS/JS files. So it works with every web technology out there.
Another thing is that ASP.NET (at least, old one, before MVC) is relying heavily on server controls. So it could be problematic to apply twitter stylesheets and behaviour to asp.net server controls. I don't know if it got any better in modern asp.net.
As long as you use regular HTML markup to define your UI and some Javascript to bring life to it, you should be fine.
Twitter's bootstrap is used for presentation and doesn't have to do anything with any programming language. You can use the bootstrap in any project using any language provided that you include the bootstrap.css stylesheet and use the CSS classes included accordingly, so there should be no concerns over whether the bootstrap will "transfer over to ASP" or any other language.
You can apply the Bootstrap CSS classes to ASP.NET controls using the CssClass parameter:
<asp:Button id="btnExample" runat="server" CssClass="btn btn-default" Text="Example" />
Related
I'm liking the Razor syntax that Microsoft has developed for inline coding in their WebMatrix product (http://en.wikipedia.org/wiki/Microsoft_WebMatrix).
Now that Visual Studio SP1 has RTM'd, is it possible (and/or planned) to enable the use of Razor syntax in ASP.NET Webforms?
We (the ASP.NET team) currently have no plans to support the WebForms page model using Razor syntax. Furthermore it is unlikely that we would ever seriously consider this as the models are too different to make the two work together.
You can use Razor pages without MVC; this is called ASP.Net WebPages.
Just add .CSHTML files to a normal ASP.Net 4.0 project.
I explained how this works in my blog.
You could possibly integrate it using the RazorEngine available from Codeplex. It allows you to process razor outside of MVC. Though you don't get all the features you get from the MVC version of Razor, such as #Html and #Url and others.
I dare say that Microsoft have considered it, but there is no official word on the subject. Since you are not supposed to have C# or VB code in the ASPX file, you have to wonder about the point of adding Razor support to Web Forms. The code behind would still be a (partial) class file. You wouldn't put Razor there any more than you would put it in a class file in Web Pages or MVC. And swapping Server Controls and all that good declarative stuff for Html Helpers removes one of the key reasons for going the Web Forms route, IMO.
This really isn't that difficult to do. Working on it right now. Grab RazorEngine from CodePlex. It lets you compile Razor cshtml/vbhtml files into a class at runtime.
You can then take that class, and use it from a ASP.Net server control, inside its Render method. This is a great way to get HTML out of the body of a server control. Much, much cleaner.
Now, you can also add some methods that you can invoke from Razor. For instance, add something like RenderChild. Additionally, you could set the Server Control itself as the Model available to Razor. You could then invoke into the server control. Including doing something like grabbing one of it's child controls and invoking Render.
I can easily localize any inline text by using
<asp:Localize runat="server" meta:resourcekey="LocalizeResource5" Text="Actions"></asp:Localize>
Is it possible to localize Html attributes directly in aspx code, without using code-behind or other “tricks”? (I mean: supported by Visual studio Resource files generator)
Example:
<input type="text" placeholder="text to localize" />
Thanks
After my experience with localizing quite few websites, I can tell you that ASP.NET localization system is pretty bad (would use some other word here... but must resist the temptation).
You've ran into one problem... for me the bigger problem was changing localized text without forcing user to reload the page.
So, what I would advise you is to ditch ASP.NET localization and switch to something way better, namely Angular-Translate.
Unlike ASP.NET localization system, Angular-Translate has seen WAY much more usage in production and most of the problems you'll run into have already been solved in the library. Plus, you can use it pretty quickly, without much AngularJs knowledge - just see getting started example.
I have a button
<input type="submit" value="Click Me" onclick="substitute()"/>
In one of my first HTML5 pages. Is there anyway I can write the body of the substitute method in C# code?
Or is it that I have no other option other than JavaScript?
The only way to have C# respond to a web page is to POST the page to a web server, or execute an AJAX request. On the web server side, your request will execute some method that contains C# code.
But it really depends on what you are trying to do; some things are better handled in the browser. Study up on ASP.NET MVC and Javascript, and your strategy will become clearer.
There are some tools that you can use to write code in C# that will be run in the browser. However this requires automatic translation of C# into JavaScript (as only JS is supported by all browsers). This maybe useful if you want to share code in C# between your Desktop app and Web app. The drawback is that any error on the page will be in the auto-generated JavaScript and you will have to somehow map this to your C# code, which may be hard.
Take a look on:
JSIL
Saltarelle
You can find more information in the Miguel de Icaza blog post:
http://tirania.org/blog/archive/2012/Sep-06.html
Like an alternative, I can offer you to look on
TypeScript which is JavaScript language's superscript, with the syntax comfortable for C# developers made by Microsoft.
Very interesting and promising project, but still in active development, as far as I know, so keep an I on regressions and retrocompatibility, if you decide to you use it.
Hope this helps.
I realize this is probably a fundamental thing I should know but I am self-teaching myself C# and asp.net so I am a little lost at this point.
I right now have 2 pages. One is an .aspx (with aspx.cs file included) that is blank and html is generated for it from a Page_Load function in the cs file. The HTML is very simple and it is just an image and some text.
The second file is a shtml file which has lots of things, serverside includes, editable and noneditable areas. I want to put my webapp into this file. My asp.net app uses Response.Write to just write out the html. This does not flow well with this page as all that does is write it at the top of the page which is because it is ran first and generates it at the top.
How can I make it to where I can generate HTML code inside the page, like within a specific DIV so it does not mess up the page. Where would a starting point be in learning how to do that.
I should note that I do not need any interaction from the user. All of this should generate right away.
I think you need to read up on some basic ASP.Net documentation and tutorials. Response.Write is not the correct approach - you need to understand how the ASP.Net page lifecycle works and how WebControls are used to render the html.
ASP.Net tries to abstract away having to create your html manually for the most part.
So if i have understood the questions correctly.
You already have an existing page/application (the shtml file) that you want to extend with some new ASP.NET components by including output from the ASP.NET page in the existing page?
This is as not something that is out of the box "supported" by ASP.NET and you "won't" be able to execute the aspx page using SSI. But you can do the opposite, an ASP.NET page does support SSI. So if you are not using any other scripts in the shtml file this might be a solution.
Otherwise the only common solutions would be either to use an AJAX framework and let it call the ASP.NET from within the existing pages or to use an iframe solution. In both cases the client will be resposible for making the calls to the ASP.NET pages and merging the results.
And then you have a issue with controlling the output from the ASP.NET page?
The Polymorphic Podcast has a good article on Controlling HTML in ASP.NET WebForms .
You can add a Literal control to the page inside the div:
<div>
<asp:Literal ID="litMarkup" runat=server />
</div>
then in your code-behind:
litMarkup.Text = "<strong>Your markup</strong>";
I don't know how well this would work for you, but could you try using an iframe to house the ASP.NET page? This should keep it in the specified region and not overwriting your shtml file. It may be something to think about.
If it is necessary that you generate your HTML output from C# code, and you would use this in more than one place, I think you may be thinking of something like what are called ASP.NET Custom Controls (not to be confused with "User Controls"-- though you probably could put together a solution with those as well, using a Literal control as another person suggested). The MSDN documentation would be a good starting point. In general, though, the writing-out-HTML-yourself-from-code model (like you would with, say, CGI applications), is not the usual ASP.NET model of development, as it largely defeats the point of using ASP.NET at all. You'd mostly want to do this sort of thing if you are writing your own web control, though this might be exactly what you are doing (hard to tell from the description).
I am a ASP.NET 3.5 web developer using VS 2008. I just started at a new company and there are alot of Web Designers here (never worked with Web Designers before). They all use Dreamweaver CS3 and PhotoShop (something i know nothing about).
What I would like to know is the following:
Would they have problems opening my ASP.NET pages in Dreamweaver? ( I heard they might not be able to ).
What about when i use MasterPages? Will they be able to open my pages when i use MasterPages, or must i stay away from MasterPages?
Thanks in advance!
They will be able to work with the markup in your aspx pages, as long as you aern't using complex server controls. Keep the markup fairly simple and you'll be OK. With master pages, they should be able to handle the layout stuff they need, and leave you to worry about the content areas. If you have the opportunity, try to go down a MVC route, this way you are encouraged to keep the code and the markup separate, and the designers will have an easy time seeing your aspx and ascx markup. Designers aren't evil, just different :)