asp.net source code blog

Hi friend,

first, sorry the rarely blog postings recently.

I've spend a while for working on a new site:

www.Dev-The-Web.com

It just tries to understand what are you coding right now ? :)

I'll be very thankful to hear your opinions about it :)

P.S. While I was working for the new site, I learn a lot of new things that I'll share as post soon :)

Best Regards,

Tihomir Ivanov

Wow, Visual Studio 2010 is coming, here's list of the features:

1. Enhanced User Experience

- Clear UI Organization
- Reduced clutter and complexity
- Improved editor
- Better support for floating documents and windows
- Enhanced document targeting
- Focused animations for action feedback

2. SharePoint Development in Visual Studio 2010

- Customizing SharePoint with the help of new project and item templates.
- Creating Web parts and application pages using new visual designers.
- Designing association and initiation forms for your workflows.
- Aggregating and integrating back-end data into your application using Business Data Catalog (BDC) models.
- Importing existing solution packages (.wsp files) and then modifying and extending them.
- Customizing features and packages using new designers and explorers.
- Deploying and debugging SharePoint applications as easily as pressing F5.
- Navigating SharePoint sites using Server Explorer.

3. Democratizing Application Lifecycle Management

- Discover and identify existing code assets and architecture with the new Architecture Explorer
- Design and share multiple diagram types, including use case, activity and sequence diagrams
- Improve testing efforts with tooling for better documentation of test scenarios and more thorough collection of test data
- Easily identify and run only the tests impacted by a code change with the new Test Impact View
- Enhanced version control capabilities including gated check-in, branch visualization, and build workflow

4. Inspiring Developer Delight

- Understand existing (and write new) code
- Intuitive Web development from the back-end to the end result
- Wrangle disparate C++ code into one arena
- Build new Windows® 7 applications or upgrade existing applications
- Enable Office tools to make your solutions more flexible and productive for specific needs

...

I didn't find nothing about LINQ approvements, but let's hope that LINQ in .NET Framework 4.0 will be better :)

Learn more HERE

Hi all,

I've just launch an asp.net related sites index. I'll try to create an index of all asp.net related sites - general, communities, blogs, forums, hosting, etc. I'll be very thankful to hear your opinion about it, could it be useful to someone or I've just lost my time :)

If you're owner of an asp.net related site, you can send me info about it to add it to the asp.net index.

Thanks in advanced for all replies :cool:

Hi all,

I've started a new site for free online tests for developers - asp.net, .net framework, css, javascript, sql, php, etc.

link: Free Online Tests

I'll be very thankful to hear your opinions about the site - design, idea, what can be improved, etc.

Thanks

Let's begin with an example of simple asp.net code:

<asp:ImageButton ID="_imgBtn" runat="server" ImageUrl="~/images/Img.jpg" Height="50px" 
Width="50px" BorderWidth="0px" BorderStyle="None" />


That's a valid asp.net code and it works fine, BUT when you try to validate it 
through W3C (http://validator.w3.org/) you will see error like this:

Error Line X column X : there is no attribute "border".

This is a problem caused by W3C running validation whilst reading the HTML rendered for a simple browser like Netscape !

Do you want your pages to be valid for old-fashioned browsers which nobody uses anymore?

If the answer of last question is 'No' here's a solution:

Add a BrowserFile.browser file with the content below inside an App_Browsers folder in the app's root. The section for validation tells it

to use the same code as IE 7 or Firefox will. Add this and your page should validate:

<!--
You can find existing browser definitions at
<windir>\Microsoft.NET\Framework\<ver>\CONFIG\Browsers
-->
<browsers>
<browser id="NewBrowser" parentID="Mozilla">
<identification>
<userAgent match="Unique User Agent Regular Expression" />
</identification>

<capture>
<userAgent match="NewBrowser (?'version'\d+\.\d+)" />
</capture>

<capabilities>
<capability name="browser" value="My New Browser" />
<capability name="version" value="${version}" />
</capabilities>
</browser>

<browser refID="Mozilla">
<capabilities>
<capability name="xml" value="true" />
</capabilities>
</browser>
<browser id="w3cValidator" parentID="default">
<identification>
<userAgent match="^W3C_Validator" />
</identification>

<capture>
<userAgent match="^W3C_Validator/(?'version'(?'major'\d+)(?'minor'\.\d+)\w*).*" />
</capture>

<capabilities>
<capability name="browser" value="w3cValidator" />
<capability name="majorversion" value="${major}" />
<capability name="minorversion" value="${minor}" />
<capability name="version" value="${version}" />
<capability name="w3cdomversion" value="1.0" />
<capability name="xml" value="true" />
<capability name="tagWriter" value="System.Web.UI.HtmlTextWriter" />
</capabilities>
</browser>
</browsers>

That's All :) Happy Coding :)

We've received some mails form our visitors, they asked us why we need to collect their names and e-mails when they download our free products. We've really don't need users names and e-mails. That's why we removed all fields for downloading our free products:

To download a product, just click on the 'Download NOW' button.

That's all. We hope to make your visits here more and more comfortable :)

Design patterns were introduced in Erich Gamma, Richard Helm, Ralph Johnson,
and John Vlissides’s seminal work Design Patterns: Elements of Reusable Object-
Oriented Software (Addison-Wesley).
There are only 23 classic patterns, and a good programmer can learn
the names and uses of all of them with some practice.
These core patterns address issues in mainline object-oriented programming (OOP),
and the original implementations were presented in C++ and Smalltalk (the primary
OOP languages at the time they were developed). Since then, other books have
implemented the patterns in Java, Visual Basic, and C#. As the value of the pattern
concept has become accepted, new patterns have been proposed to add to the
original list. In addition, there are now patterns that are applicable to specific areas,
such as software architecture, user interfaces, concurrency, and security. Although
these patterns are extremely important in their areas, their adherents are fragmented,
and the core set of universally accepted patterns has not been expanded.
The 23 patterns are divided into three groups: creational, structural, and behavioral.

Creational Patterns

The creational patterns aim to separate a system from how its objects are created,
composed, and represented. They increase the system’s flexibility in terms of the
what, who, how, and when of object creation. Creational patterns encapsulate the
knowledge about which classes a system uses, but they hide the details of how the
instances of these classes are created and put together. Programmers have come to
realize that composing systems with inheritance makes those systems too rigid. The
creational patterns are designed to break this close coupling.

Structural Patterns

Structural patterns can be employed while a system is being designed, or later on
during maintenance and extension. In fact, some of them are specifically useful in the
post-production stages of the lifecycle of a software system, when changes are introduced
that were not foreseen and when even the interfaces between components
need updating. Thus, sometimes when you want to add functionality, you will be
working with existing classes that cannot be changed.

Behavioral Patterns

Behavioral patterns are concerned with algorithms and communication between
them. The operations that make up a single algorithm might be split up between different
classes, making a complex arrangement that is difficult to manage and maintain.
The behavioral patterns capture ways of expressing the division of operations
between classes and optimize how the communication should be handled.