iMadalina on .Life

Oare chiar "a murit" VB .NET? Se spune ca am intrat in "era C#"... Ca echipa de VB .NET de la Redmond este formata numai din "impatimiti" si ca restul lumii foloseste C#. Oare este chiar asa?

Cautam pe net un exemplu de cod pentru display intr-un GridView al imaginilor luate dintr-o daza de date unde sunt stocate ca sit de biti. Zis si facut. Am gasit exemple, insa 90% din ele in VB .NET. CodeGuru, ASP Alliance, CodeSource si toate site-urile de gen. Am gasit intr-un final si cod in C#, insa de salvare a imaginilor in SQL si nu de citire. Si nu este prima oara cand, cautand un exemplu pe net, gasesc numai VB.

Sa fi murit oare VB .NET?

The Web.config file of a web application can also be modified programatically. For example, if you want to modify the app's configuration data, you use:

Configuration config = WebConfigurationManager.OpenWebConfiguration(Request.ApplicationPath);

config.AppSettings.Settings["key_value"] = "...";

config.Save();

But what you must remember is that, every time the Web.config is modified and a new version is saved, a new Application Domain will be created for the next Session of the application. So the next user of the web application will run his session in a different environment, with new application state, session state and cache variables.

Every aspx page has an "AutoEventWireUp" property. By default this is set to 'True'.

'True' means that events with a certain name are automatically linked to the objects that trigger them. 'False' signifies that in the page there can also be events that are not linked to a control. These events, however, can be linked to controls using delegates. Why would we want this? Because there are cases in which the controls are added in the page dynamically and can only be linked to events in code.

Ce ati alege?

1. sa lucrati la un proiect in care sa aveti mai multe roluri si sa "puneti mana" pe mai multe tehnologii ?
2. sa lucrati la un proiect in care sa va ocupati de un singur modul si sa aveti responsabilitate exclusiva pentru el ?

Cu toate aspectele incluse: un rol vs mai multe, cunostinte legate de o singura tehnologie vs mai multe, responsabilitate, lucru in echipa, absenta/prezenta unui leader de proiect, arhitectura vs coding...