I guess I just never took the time to wrap my head around it and stop asking "Why". I've tried to learn it before and it was *meh*, I'll just go with another technology...but now I'm kinda being shoved into it.

Seriously it's depressing to get an interview for a Senior Developer position, and when they ask "What happens on page postback?", and I say "Unfortunately I don't write in that manner" and I hear "Oh, um, hmm, well that's how you do it in .NET"

I feel like I'm losing my mind, I KNOW I'm Senior/Lead material, I just don't use it the "legacy", way (before jQuery came along and made everyone's life easier)?

That's what I do now. Kinda not acceptable, that's why I'm in this place.

Web - No problem, Server - No Problem, HTTP - No problem, most positions no problem. As a developer I've gotten WinForms work done, Web work done, etc.

ASP.NET is killing me. I have no idea what my break in thinking is....

I understand that <? ?> is pretty much equal to <% %> and etc....however as I'm trying to go  back and learn things...Microsoft is introducing Razor, etc. So I'm going from trying to learn to wrap things in <form> and <asp:TextBox> to normal <input type="text" />. In other words I need to break what I know, to learn what I need, to learn that I need to use what I've been.

Mentally I'm exhausted and I don't know what to do.

If you needed Vista to develop for Windows Phone not one company would have written anything.

My company isn't ready to move to Windows 8, but we want to develop for Windows Phone.

wut do?

@CODE
      Dim qfilter = Request.Form("qfilter").ToString
      Dim q = Request.Form("q").ToString
      Dim db = Database.Open("myConnectionString")
      Dim selectQuery = "SELECT * FROM table_name WHERE @0 = @1"
      For Each row in db.Query(selectQuery,qfilter,q)
          'Code to show results
      Next
END CODE

However I'm not getting any results back....when I output the variables I'm getting the @0 and @1 the way they should be (Payroll and 7748 respectively), however inside the page nothing else is happening.

Ideas?

I have a connection to a remote server that has a table with some data (all imported). However the column names have spaces in them. So when I perform my query...

@For Each row in db.Query(QueryString)

Next

I'm trying to create a row in a table using @:<tr><td>@row.x</td></tr>, however it's failing when x has a space in it. Additionally I tried @row.[x] and it still fails. Any ideas? Or a article/page that can point me in the right direction?

Thanks.

Is there any idiots guide to writing toolbox controls (user controls)? From within VB? If needed I'll write the HTML5 elements as controls for my team... thanks.

This tactic sounds more like spyware/virus than any feasible reason....but hmm

I've found different articles on writing classes to use myself but how's this not baked in yet?

http://www.aspspider.com/qa/Question4562.aspx

Which talks about taking parts out of the web.config.... wha? Why?

Our main site is .NET 2.0 and our app is .NET 4.0 we're trying to make our app a child site from the main default however we're getting an error message...

"The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework"

But we have that all taken care of...is there a way IIS needs to be configured for this?

Kidding I've been here before, just now in a position to make a new appearance.

stevo_ said:

None of the above.

Dexter said:

W3bbo said:

*snip*

Tipically the "sender" is the object that raised the event, in this case this is the menu item and not the link label.

W3bbo said:

Cybermagellan said:

*snip*

Whilst it's too late for WinForms, I think Microsoft should rethink the semantics of their UI event standards. It seems very tied in to specific HCI devices rather than what the event really describes; I equate it to the presentational attributes in HTML that have since been removed.

Take Button.Click for example, on the surface it sounds fine since you use a mouse button to click on a button, but buttons can be triggered in other ways: the space bar on your keyboard, in program code directly, or a tablet tap just to name a few. Then there's some inconsistency since some events are fired on button-down, others on button-up. I'd prefer a neutral replacement: "Button.Press" which frees it from the relationship with the mouse and accuracy conveys how the event is related to the button actually being pressed.

Also note how .Click is the main event for the Button class, yet the .Click event on other controls is meaningless: you can click on a Checkbox but not change its state (that's why we use .CheckChanged) or on ComboBox controls (which is where it gets complicated because there's several events for the same thing, just subtly different, see: SelectedIndexChanged, SelectionChangeComitted, and SelectedValueChanged.

I agree....SelectedIndex and SelectedText can get confusing...I know for awhile I was wondering why a SelectedItem wasn't working when I was clearly selecting some text in a ComboBox....yeah....

So question...

I'm trying to perform an action on the ContextMenu item associated with the LinkLabel....now since this is a twitter feed I have 20 LinkLabels....but my LinkEvent pretty much looks valid...

private void menuItem_Click(object sender, EventArgs e)
{
MessageBox.Show(((LinkLabel)sender).Name);
}

but I'm getting an error with casting from a LinkLabel to a MenuItem....what am I missing here or is it that the contextMenuStrip MenuItem doesn't pass along the objects property that I've used it with? LinkLabel.ContextMenuStrip = MenuStrip..blah...

CannotResolveSymbol said:

W3bbo said:

*snip*

Memory management in ObjC isn't that difficult (just release objects you own when you're done with them; the runtime handles reference counting and deallocation for you).  The tricky part comes in the other aspects of an unsafe language:  the language is a strict superset of C, with all the dangers thereof (like the mess you can cause if pointers are mishandled).

Why .NET developers? I mean that's like saying you're gonna take a bunch of Nascar drivers and teach them to drive motorcycles...but not give them a motorcycle or a garage to put it in...

Unless you give those .NET developers a Mac, an iPhone/Pod, and a dev subscription you may be barking up the wrong tree.