Tout est encore nouveau pour moi avec Visual Studio… cependant les premiers problèmes que j’ai ressentis trouvent leurs solutions dans la prochaine version. Ça fait plaisir.

Moins de problèmes avec Visual Source Safe

To better support both of these scenarios, VS 2005 web projects no longer store a list of all files in a central web project manifest file. Instead, the content and layout of the web project are directly inferred from the file-layout and file contents of the web-project folder. Additions/deletions/movements of files and folders within the web-project do not require updating one central project file that is a single point of contention. This means you can easily use any non-VS tool that directly works off the file-system with your web project, and that when running under source control you do not need to lock and update the project file anytime you move or make a file change. src

Unit testing

Les tests unitaire vont enfin être intégré à l’environnment de développement. Il sera testé les scripts écrits en ASP.net. Je n’ai rien trouvé quant aux Javascripts côté client.

1) Ability to develop unit tests for both classes and web UI within a web project (allowing functional ASP.NET UI validation within test projects). VSTS includes a built-in web replay tool that captures interactions between a browser and the server, and allows easy automation and validation of behavior.

il sera aussi possible de connaître la quantité de code couverte par les tests unitaire. Je trouve ça très utile lors de l’implantation de tests pour une application qui n’en a pas encore.

2) Ability to measure and precisely quantify the percentage of code exercised by tests (what we often call code coverage). A web developer can build a web project, then build lots of tests to exercise its functionality, and can then run those tests and get a report detailing that “74% of the lines of code in the web project were executed during the tests”, as well as a precise breakdown of what parts of the code-base were not exercised because boundary and use cases weren’t good enough. src

une manière de comprendre nos problèmes de performance

4) Ability to profile code execution of web projects, and analyze the % of time spent where within a web project as well as memory allocations and usage.

Livraison facilité.

The optional ability to completely compile a web project, including compiling all .aspx, .ascx, and .master file content (allowing you to compile and then remove the HTML and ASP.NET server control markup code, and optionally even remove the .aspx and .ascx files themselves and just ship the .dll assemblies). There are a couple of benefits with this feature: 1) It allows you to ship a totally “locked-down” deployment package for enterprise deployment environments. 2) It allows you to better protect your intellectual property from customers if you don’t want them to see or change your markup. 3) It eliminates all runtime ASP.NET compilation steps, avoiding the first-time performance hit when a page is first accessed and the .aspx markup is compiled, and enabling much better application startup time and working set usage. This later benefit can be particularly noticeable with large applications, and provides a big performance improvement over VS 2003 built apps today. src

VS 2005 and ASP.NET 2.0 now have richer support for command-line level build automation, and can also be integrated and automated using the new MSBuild system being introduced in VS 2005.

sur SharePoint

Sharepoint Server Support

We’ve done a lot of work to integrate ASP.NET 2.0 with the next release of Sharepoint that ships with Office 12 next year. The new version is built entirely using the new feature of ASP.NET 2.0: WebParts, Master Pages, Themes, Site Navigation, Membership, Roles, Personalization, Localization, Data Controls, etc.

One of our goals with Visual Studio is to enable great tool support for building Sharepoint solutions. Today with VS 2003 this is fairly limited (you can pretty much only create a web-part control as a class library). One of the design goals of the new VS 2005 web project system was to enable great Sharepoint support, and enable directly opening and debugging Sharepoint solutions. Going forward we will support creating and editing new pages in running Sharepoint servers, support adding code-behind logic to pages, creating application logic, customizing workflow, building and adding new webpart controls, and debugging the finished solution.

Prochainenement il sera systèmatiquement proposé à l’ajout dans VSS comme il est un sous répertoire du projet.

For temporary file storage that is dynamically generated underneath a web-project or web-root, you might want to consider using hidden folders.

Directory.CreateDirectory("tempstorage");
File.SetAttributes("tempstorage", FileAttributes.Hidden);