What is the difference between c#.net and vb.net ?
I faced this question in an interview. Any technical difference is there ? I heard that there are two methods additional in vb.net which are not there in vb.net.
I thought that <%: had replaced <%=, since mentions on [URL]Prior to ASP.NET 4, the <%= %> syntax was used to execute code and write it out to the page. Starting with ASP.NET 4, you should always use the <%: %> syntax instead..."
I hope this isn't too much of a newbie question. I seem to always use the correct syntax, but I don't really understand why I'm using the <%: and <%= in ASP.NET, and I was hoping someone could clarify for me. I found this article which explains <%= and <%#, but wasn't able to find anything in Google on <%:.
I am in the process of learning MVC, and thought I would parallel the work in both C# and VB.NET. I ran into a snag when right-clicking in an action method inside of a controller to add a view - in C# if I choose to strongly type the view it includes all the objects in the models folder in the drop-down list for selection; however, in VB.NET none of the models are available in the list. Is there some step I need to take in order to make the models objects available in the drop down for selection?
I'm starting to learn ASP.NET and going through the tutorial videos on www.asp.net. I understand the basic concept of web application frame works like ASP/PHP/ASP.NET. HTML/XHTML is created with special tags that the server knows to read and replace with content. I did a little bit with ASP during a summer internship back in the 90's.
Yet with the few examples of ASP.NET I've seen so far it seems ASP.NET has two types of server interpreted tags.
but I also see regular ASP tags like <%@ Master Language="C#" AutoEventWireup="true" CodeBehind="Site.master.cs" Inherits="TailspinSpyWorks.SiteMaster" %>
What is the difference between these two tag formats? Both are interpreted by the server correct? Why would I use one over the other?
Have a C# application. When I look in the project folder I see an .exe in bin/debug folder, when I click it executes the application fine. I also see the same .exe in obj/debug folder, when I click it executes but gives me error. What is the difference between these 2 objects and why do I have 2 of them?
I want to build my own web framework, and I want to build it in C#. I figure the easiest way to get started is to use ASP.NET to handle all the server communication stuff. The rest I want to build my self. I know next to nothing about ASP.NET. (But know C#, the MVC pattern, and other web frameworks quite well).
In Visual Studio 2010 I see
ASP.NET Web Application ASP.NET MVC 2 Empty Web Application ASP.NET MVC 3 Empty Web Application
I figure one of these should be good as a base. I just want some "entry point" into some C# code. I started with PHP so it's a little bit weird for me to not be able to just load up a file in my browser. Anyway, which should I use? What's the difference between a plain ASP.NET Web App and an empty MVC 3 app? If it's "empty" it shouldn't be using any of the MVC framework, should it? I just want to make sure I use the latest and greatest "ASP" for handling the server stuff before I embark down this road.
which is future of web technology of microsoft silverlight or mvc asp.net i am really confused iam good in asp.net but completely unaware with silvelight and mvc
I have the project in vs2008. I find that there is difference behavior between VS2008 Debug Mode IIS and Windows 7 IIS.
I have published the project and deploy on windows 7 IIS.
Different examples: After login, VS2008 debug mode can go to default page but not in windows 7 IIS in which it return back to login page after login. Sometimes, they can login but still difference behavior in page reload such as dropdownlist databind.