Visual Studio .NET IDE
Visual Studio .NET IDE (Integrated Development Environment) is the Development Environment for all .NET based applications which comes with rich features. VS .NET IDE provides many options and is packed with many features that simplify application development by handling the complexities. Visual Studio .NET IDE is an enhancement to all previous IDE’s by Microsoft.
Important Features
One IDE for all .NET Projects
Visual Studio .NET IDE provides a single environment for developing all types of .NET applications. Application’s range from single windows applications to complex n-tier applications and rich web applications.
Option to choose from Multiple Programming Languages
You can choose the programming language of your choice to develop applications based on your expertise in that language. You can also incorporate multiple programming languages in one .NET solution and edit that with the IDE.
IDE is Customizable
You can customize the IDE based on your preferences. The My Profile settings allow you to do this. With these settings you can set the IDE screen the way you want, the way the keyboard behaves and you can also filter the help files based on the language of your choice.
Built-in Browser
The IDE comes with a built-in browser that helps you browse the Internet without launching another application. You can look for additional resources, online help files, source codes and much more with this built-in browser feature.
When we open VS .NET from Start->Programs->Microsoft Visual Studio .NET->Microsoft Visual Studio .NET the window that is displayed first is the Start Page which is shown below. The start Page allows us to select from the most recent projects (last four projects) with which we worked or it can be customized based on your preferences.
The Integrated Development Environment (IDE) shown in the image below is what we actually work with. This IDE is shared by all programming languages in Visual Studio. You can view the toolbars towards the left side of the image along with the Solution Explorer window towards the right.
New Project Dialogue Box
The New Project dialogue box like the one in the image below is used to create a new project specifying it's type allowing us to name the project and also specify it's location on the disk where it is saved. The default location on the hard disk where all the projects are saved is C:\DocumentsandSettings\Administrator\MyDocuments\VisualStudioProjects.
Following are different templates under Project Types and their use.
Windows Application: This template allows to create standard windows based applications.
Class Library: Class libraries are those that provide functionality similar to Active X and DLL by creating classes that access other applications.
Windows Control Library: This allows to create our own windows controls. Also called as User Controls, where you group some controls, add it to the toolbox and make it available to other projects.
ASP .NET Web Application: This allows to create web-based applications using IIS. We can create web pages, rich web applications and web services.
ASP .NET Web Service: Allows to create XML Web Services.
Web Control Library: Allows to create User-defined controls for the Web. Similar to user defined windows controls but these are used for Web.
Console Application: A new kind of application in Visual Studio .NET. They are command line based applications.
Windows Service: These run continuously regardless of the user interaction. They are designed for special purpose and once written, will keep running and come to an end only when the system is shut down.
Other: This template is to develop other kinds of applications like enterprise applications, database applications etc.
Wednesday, May 9, 2007
Friday, May 4, 2007
What is Green Architecture?
What is Green Architecture?
An introduction to Green Building and a description of the way in which the ARC Design Group strives to meet the goals of Green Building.
First and foremost, a green building serves the needs of the people who inhabit it. It supports and nurtures their health, satisfaction, productivity, and spirit. It requires the careful application of the acknowledged strategies of sustainable architecture — non-toxic construction, the use of durable, natural, resource efficient materials, reliance on the sun for daylighting, thermal and electric power, and recycling of wastes into nutrients. An elegant architectural integration of these strategies produces a building which honors the aspirations of those who use it and engages the natural world. And it must be more.
We recognize that the conversion of our culture to a sustainable basis involves a fundamental transformation of the human spirit. We must rediscover our interconnectedness and interdependence with something much larger than ourselves: the natural world (on the material plane) and the spiritual realm which transcends it. Bo Lozoff has called the first community and the second communion, and he suggests that we must have both to be truly at home in the world.
Community supports sustainability. Certain key strategies of a sustainable society can only be sensibly implemented at a larger scale than a single building. Examples of this in the Northeast bioregion are annual cycle solar energy storage and district heating, solar aquatic waste treatment, bioshelters, and clean cogeneration of electrical and thermal power from biomass. Given this, ARC has been actively involved in community building in the areas of cohousing, sustainable business, and in the architectural design process itself.
We believe that excellence in environmental design can only arise from a truly integrated design team — a community of designers. ARC has taken the first step by forming an architectural partnership which consists of an architect, an engineer, and a designer/builder/businessperson. Ultimately the community of designers must include all the stakeholders in the project — everyone becomes a designer, and contributes a unique wisdom to the whole. The participatory design process becomes a powerful method of community building. It is a central aspect of our work with our clients. Most buildings are designed as a settlement between the various designers, each defending their own turf. The settlement is produced by compliance. But co-operation — inviting others to the table — yields a different result, and we replace the current relay-race approach to design and building with an integrated approach.
We’ve discovered important aspects of this system which are different from the conventional design process, such as:
• Schematic design should occupy roughly 40% of the design rather than the conventional 25% because systems and envelope design are so interrelated with massing and siting;
• The process is messy, thorny, and bumpy, and therefore it takes time. Integrated design requires complex thinking and testing up front, so we need to resist schedule compression;
• You can’t just plug in new technologies — synergies have to be developed, nurtured, and woven into a seamless fabric;
• The construction process requires similar integration. The adversarial, low-bid approach is a disaster, and systematically yields poor results. Builders must be brought into the design process and should be selected using the same criteria we use to select other professionals: for their skill, experience, and integrity.
• Post occupancy concern and tuning is an essential missing factor in the modern day building equation. Green buildings must be commissioned to make certain systems are operating properly, especially as we incorporate technological change and improvement.
Sustainability is so much more than solar heat and non-toxicity. The struggle to achieve it demands that we question each part of the process, while remembering that, as Paul Ehrlich says, the first rule of intelligent tinkering is to save all the parts.
A green building is often described as one which minimizes its negative environmental impact. We seek to turn that around, and aim for buildings which improve the quality of the air and water, produce surplus power and food, and convert waste into nutrients and useful products.
The Community as Client
A critical part of the success of green buildings is the client. A client is almost always made up of a community, and usually several.
One of the strengths we bring to this project is our ability to work with groups and our interest in this process. We don’t make the decisions. We design, we guide, we tug, we forage, and we elicit the community will. "The first responsibility of a leader," writes retired Herman Miller CEO Max duPree, "is to define reality." We help the client community create an insightful sense of current and future reality.
We have devoted ourselves, in recent years, to the discovery and practice of effective ways to help groups articulate who they are and what they need. Through cohousing projects, through employee-owned business ventures, through our work with a Tribal community, and our work with large communities of interest, we are beginning to learn to get the best out of group endeavors. We have witnessed charrette situations which failed to take advantage of the collective intelligence gathered for the purpose. We therefore insist on thoughtful facilitation, whether it be by us or by others whose competence exceeds our own.
As we write, one of our partners, John Abrams, is preparing to leave for an intensive session with Stewart Brand, and others, working to discover how scenario planning — a process developed to help corporations and governments understand the future — can be applied to the design process. And surely the Oberlin project will include a community of participants envisioning the future. Another partner, Bruce Coldham, has just returned from the third North American Cohousing Conference. The simulation game he invented has become a standard training tool for resident-developer cohousing groups (see illustration).
A description of our approach to a recent project may be the best way to convey our sense of the community design process.
The Northeast Sustainable Energy Association has begun a project in Western Massachusetts with far-reaching goals. ARC Design was hired to lead the organization through the visioning and schematic design process for the Northeast Sustainability Center. We began by holding a week-end session with staff, board, and members — about 80 persons — to establish the vision, the dream, the parameters of the project. The workshop organized, filtered, and prioritized the community’s thinking and produced a photographic record of the collective voice of the group. It was a provocative educational experience for the participants.
After the vision workshop, ARC worked with the Building Committee to create the program and a set of design objectives for the project, and then formed a Technical Resource Group. The idea was to engage a group of experts in the various realms of ecological design and request their help in testing our design objectives and suggesting how they might be achieved. From a long list of possibilities, we pared down to 15, from across the country, and one from Norway. We asked them to commit themselves to a one day meeting in the Northeast and an additional 10 hours of consulting time. We would pay their expenses only. None refused the invitation. The workshop was a day long discussion of what this project might be. Seventy five NESEA members attended. The day was a combination of plenary activity and small group work. Ideas were recorded on cards and organized on a giant pinboard. They became the basis for a series of 40 schematic design solution concepts.
All this happened before we had a site. Armed with program, objectives, and design concepts, we needed a place to go. The site search began in earnest. This would be a major test. Did the project have enough appeal that a low-overhead organization with zero equity and a few wild ideas would be able to secure real estate? Who knew? One of the project objectives was to align with local educational institutions. Another was to take advantage of existing buildings and infrastructure. Another was to be the beginning of a sustainable community. Before long, we had three solid offers — a piece of land at Hampshire College, a piece of land at the New England Small Farms Institute facility, and a building on the University of Massachusetts campus. All were attractive; all promised important affiliations and bridge building.
Then something happened. Greenfield, where NESEA has been located, is a small city whose main economic activity (tool and die manufacturing) had died. The town leaders got wind of the project and didn't want NESEA to leave. They offered to donate a 6,000 sq. ft. downtown building for NESEA to re-hab and occupy. Part of the deal was that NESEA would design and become a partner with the town in the construction of an ecological park adjacent to the building. The project extended, and some of its objectives began to be realized (re-hab a building, stimulate economic re-vitalization, integrate building with landscape and urban agriculture).
The most compelling part of the story is the developing relationship with the town of Greenfield. This unexpected twist strengthened the project immensely and sprung directly from a broad, open process that had room for new ideas. All signs point to an enduring and synergistic collaboration between the town and the organization. The park has become an important part of the project and the town’s future. As it proceeds, it may energize downtown Greenfield, it may change the transportation system, it may attract new businesses and visitors, and it may re-awaken Greenfield's strong sense of pride. This is an example of a community design process in action.
Architectural Solutions to Environmental Problems
Practiced this way, green architecture becomes a significant part of the path to a sustainable future. It brings people together in community, and thereby demonstrates and deepens our connection to each other and the natural world. These qualities uplift and nurture the human spirit — they help us discover and honor our purpose and our selves.
The development of a competent architectural integration of ecological principles promises to assist environmental restoration and healing. It also promises buildings that endure. Only buildings that endure — ones that are loved, and cherished, and cared for — will be solutions rather than problems.
Environmental problems are, above all, complex. It takes multi-level, well-linked biological inquiry to achieve understanding and resolution. If the architectural community can offer a systematic collaborative approach to such understanding, we will have built something more dynamic than just buildings. The emergence of a coherent new process might provide an important tail wind to push the long march to sustainability.
An introduction to Green Building and a description of the way in which the ARC Design Group strives to meet the goals of Green Building.
First and foremost, a green building serves the needs of the people who inhabit it. It supports and nurtures their health, satisfaction, productivity, and spirit. It requires the careful application of the acknowledged strategies of sustainable architecture — non-toxic construction, the use of durable, natural, resource efficient materials, reliance on the sun for daylighting, thermal and electric power, and recycling of wastes into nutrients. An elegant architectural integration of these strategies produces a building which honors the aspirations of those who use it and engages the natural world. And it must be more.
We recognize that the conversion of our culture to a sustainable basis involves a fundamental transformation of the human spirit. We must rediscover our interconnectedness and interdependence with something much larger than ourselves: the natural world (on the material plane) and the spiritual realm which transcends it. Bo Lozoff has called the first community and the second communion, and he suggests that we must have both to be truly at home in the world.
Community supports sustainability. Certain key strategies of a sustainable society can only be sensibly implemented at a larger scale than a single building. Examples of this in the Northeast bioregion are annual cycle solar energy storage and district heating, solar aquatic waste treatment, bioshelters, and clean cogeneration of electrical and thermal power from biomass. Given this, ARC has been actively involved in community building in the areas of cohousing, sustainable business, and in the architectural design process itself.
We believe that excellence in environmental design can only arise from a truly integrated design team — a community of designers. ARC has taken the first step by forming an architectural partnership which consists of an architect, an engineer, and a designer/builder/businessperson. Ultimately the community of designers must include all the stakeholders in the project — everyone becomes a designer, and contributes a unique wisdom to the whole. The participatory design process becomes a powerful method of community building. It is a central aspect of our work with our clients. Most buildings are designed as a settlement between the various designers, each defending their own turf. The settlement is produced by compliance. But co-operation — inviting others to the table — yields a different result, and we replace the current relay-race approach to design and building with an integrated approach.
We’ve discovered important aspects of this system which are different from the conventional design process, such as:
• Schematic design should occupy roughly 40% of the design rather than the conventional 25% because systems and envelope design are so interrelated with massing and siting;
• The process is messy, thorny, and bumpy, and therefore it takes time. Integrated design requires complex thinking and testing up front, so we need to resist schedule compression;
• You can’t just plug in new technologies — synergies have to be developed, nurtured, and woven into a seamless fabric;
• The construction process requires similar integration. The adversarial, low-bid approach is a disaster, and systematically yields poor results. Builders must be brought into the design process and should be selected using the same criteria we use to select other professionals: for their skill, experience, and integrity.
• Post occupancy concern and tuning is an essential missing factor in the modern day building equation. Green buildings must be commissioned to make certain systems are operating properly, especially as we incorporate technological change and improvement.
Sustainability is so much more than solar heat and non-toxicity. The struggle to achieve it demands that we question each part of the process, while remembering that, as Paul Ehrlich says, the first rule of intelligent tinkering is to save all the parts.
A green building is often described as one which minimizes its negative environmental impact. We seek to turn that around, and aim for buildings which improve the quality of the air and water, produce surplus power and food, and convert waste into nutrients and useful products.
The Community as Client
A critical part of the success of green buildings is the client. A client is almost always made up of a community, and usually several.
One of the strengths we bring to this project is our ability to work with groups and our interest in this process. We don’t make the decisions. We design, we guide, we tug, we forage, and we elicit the community will. "The first responsibility of a leader," writes retired Herman Miller CEO Max duPree, "is to define reality." We help the client community create an insightful sense of current and future reality.
We have devoted ourselves, in recent years, to the discovery and practice of effective ways to help groups articulate who they are and what they need. Through cohousing projects, through employee-owned business ventures, through our work with a Tribal community, and our work with large communities of interest, we are beginning to learn to get the best out of group endeavors. We have witnessed charrette situations which failed to take advantage of the collective intelligence gathered for the purpose. We therefore insist on thoughtful facilitation, whether it be by us or by others whose competence exceeds our own.
As we write, one of our partners, John Abrams, is preparing to leave for an intensive session with Stewart Brand, and others, working to discover how scenario planning — a process developed to help corporations and governments understand the future — can be applied to the design process. And surely the Oberlin project will include a community of participants envisioning the future. Another partner, Bruce Coldham, has just returned from the third North American Cohousing Conference. The simulation game he invented has become a standard training tool for resident-developer cohousing groups (see illustration).
A description of our approach to a recent project may be the best way to convey our sense of the community design process.
The Northeast Sustainable Energy Association has begun a project in Western Massachusetts with far-reaching goals. ARC Design was hired to lead the organization through the visioning and schematic design process for the Northeast Sustainability Center. We began by holding a week-end session with staff, board, and members — about 80 persons — to establish the vision, the dream, the parameters of the project. The workshop organized, filtered, and prioritized the community’s thinking and produced a photographic record of the collective voice of the group. It was a provocative educational experience for the participants.
After the vision workshop, ARC worked with the Building Committee to create the program and a set of design objectives for the project, and then formed a Technical Resource Group. The idea was to engage a group of experts in the various realms of ecological design and request their help in testing our design objectives and suggesting how they might be achieved. From a long list of possibilities, we pared down to 15, from across the country, and one from Norway. We asked them to commit themselves to a one day meeting in the Northeast and an additional 10 hours of consulting time. We would pay their expenses only. None refused the invitation. The workshop was a day long discussion of what this project might be. Seventy five NESEA members attended. The day was a combination of plenary activity and small group work. Ideas were recorded on cards and organized on a giant pinboard. They became the basis for a series of 40 schematic design solution concepts.
All this happened before we had a site. Armed with program, objectives, and design concepts, we needed a place to go. The site search began in earnest. This would be a major test. Did the project have enough appeal that a low-overhead organization with zero equity and a few wild ideas would be able to secure real estate? Who knew? One of the project objectives was to align with local educational institutions. Another was to take advantage of existing buildings and infrastructure. Another was to be the beginning of a sustainable community. Before long, we had three solid offers — a piece of land at Hampshire College, a piece of land at the New England Small Farms Institute facility, and a building on the University of Massachusetts campus. All were attractive; all promised important affiliations and bridge building.
Then something happened. Greenfield, where NESEA has been located, is a small city whose main economic activity (tool and die manufacturing) had died. The town leaders got wind of the project and didn't want NESEA to leave. They offered to donate a 6,000 sq. ft. downtown building for NESEA to re-hab and occupy. Part of the deal was that NESEA would design and become a partner with the town in the construction of an ecological park adjacent to the building. The project extended, and some of its objectives began to be realized (re-hab a building, stimulate economic re-vitalization, integrate building with landscape and urban agriculture).
The most compelling part of the story is the developing relationship with the town of Greenfield. This unexpected twist strengthened the project immensely and sprung directly from a broad, open process that had room for new ideas. All signs point to an enduring and synergistic collaboration between the town and the organization. The park has become an important part of the project and the town’s future. As it proceeds, it may energize downtown Greenfield, it may change the transportation system, it may attract new businesses and visitors, and it may re-awaken Greenfield's strong sense of pride. This is an example of a community design process in action.
Architectural Solutions to Environmental Problems
Practiced this way, green architecture becomes a significant part of the path to a sustainable future. It brings people together in community, and thereby demonstrates and deepens our connection to each other and the natural world. These qualities uplift and nurture the human spirit — they help us discover and honor our purpose and our selves.
The development of a competent architectural integration of ecological principles promises to assist environmental restoration and healing. It also promises buildings that endure. Only buildings that endure — ones that are loved, and cherished, and cared for — will be solutions rather than problems.
Environmental problems are, above all, complex. It takes multi-level, well-linked biological inquiry to achieve understanding and resolution. If the architectural community can offer a systematic collaborative approach to such understanding, we will have built something more dynamic than just buildings. The emergence of a coherent new process might provide an important tail wind to push the long march to sustainability.
Thursday, May 3, 2007
VISUAL BASIC INTRODUCTION
Visual Basic .NET
Visual Basic .NET provides the easiest, most productive language and tool for rapidly building Windows and Web applications. Visual Basic .NET comes with enhanced visual designers, increased application performance, and a powerful integrated development environment (IDE). It also supports creation of applications for wireless, Internet-enabled hand-held devices. The following are the features of Visual Basic .NET with .NET Framework 1.0 and Visual Basic .NET 2003 with .NET Framework 1.1. This also answers why should I use Visual Basic .NET, what can I do with it?
Powerful Windows-based Applications
Visual Basic .NET comes with features such as a powerful new forms designer, an in-place menu editor, and automatic control anchoring and docking. Visual Basic .NET delivers new productivity features for building more robust applications easily and quickly. With an improved integrated development environment (IDE) and a significantly reduced startup time, Visual Basic .NET offers fast, automatic formatting of code as you type, improved IntelliSense, an enhanced object browser and XML designer, and much more.
Building Web-based Applications
With Visual Basic .NET we can create Web applications using the shared Web Forms Designer and the familiar "drag and drop" feature. You can double-click and write code to respond to events. Visual Basic .NET 2003 comes with an enhanced HTML Editor for working with complex Web pages. We can also use IntelliSense technology and tag completion, or choose the WYSIWYG editor for visual authoring of interactive Web applications.
Simplified Deployment
With Visual Basic .NET we can build applications more rapidly and deploy and maintain them with efficiency. Visual Basic .NET 2003 and .NET Framework 1.1 makes "DLL Hell" a thing of the past. Side-by-side versioning enables multiple versions of the same component to live safely on the same machine so that applications can use a specific version of a component. XCOPY-deployment and Web auto-download of Windows-based applications combine the simplicity of Web page deployment and maintenance with the power of rich, responsive Windows-based applications.
Powerful, Flexible, Simplified Data Access
You can tackle any data access scenario easily with ADO.NET and ADO data access. The flexibility of ADO.NET enables data binding to any database, as well as classes, collections, and arrays, and provides true XML representation of data. Seamless access to ADO enables simple data access for connected data binding scenarios. Using ADO.NET, Visual Basic .NET can gain high-speed access to MS SQL Server, Oracle, DB2, Microsoft Access, and more.
Improved Coding
You can code faster and more effectively. A multitude of enhancements to the code editor, including enhanced IntelliSense, smart listing of code for greater readability and a background compiler for real-time notification of syntax errors transforms into a rapid application development (RAD) coding machine.
Direct Access to the Platform
Visual Basic developers can have full access to the capabilities available in .NET Framework 1.1. Developers can easily program system services including the event log, performance counters and file system. The new Windows Service project template enables to build real Microsoft Windows NT Services. Programming against Windows Services and creating new Windows Services is not available in Visual Basic .NET Standard, it requires Visual Studio 2003 Professional, or higher.
Full Object-Oriented Constructs
You can create reusable, enterprise-class code using full object-oriented constructs. Language features include full implementation inheritance, encapsulation, and polymorphism. Structured exception handling provides a global error handler and eliminates spaghetti code.
XML Web Services
XML Web services enable you to call components running on any platform using open Internet protocols. Working with XML Web services is easier where enhancements simplify the discovery and consumption of XML Web services that are located within any firewall. XML Web services can be built as easily as you would build any class in Visual Basic 6.0. The XML Web service project template builds all underlying Web service infrastructure.
Mobile Applications
Visual Basic .NET 2003 and the .NET Framework 1.1 offer integrated support for developing mobile Web applications for more than 200 Internet-enabled mobile devices. These new features give developers a single, mobile Web interface and programming model to support a broad range of Web devices, including WML 1.1 for WAP—enabled cellular phones, compact HTML (cHTML) for i-Mode phones, and HTML for Pocket PC, handheld devices, and pagers. Please note, Pocket PC programming is not available in Visual Basic .NET Standard, it requires Visual Studio 2003 Professional, or higher.
COM Interoperability
You can maintain your existing code without the need to recode. COM interoperability enables you to leverage your existing code assets and offers seamless bi-directional communication between Visual Basic 6.0 and Visual Basic .NET applications.
Reuse Existing Investments
You can reuse all your existing ActiveX Controls. Windows Forms in Visual Basic .NET 2003 provide a robust container for existing ActiveX controls. In addition, full support for existing ADO code and data binding enable a smooth transition to Visual Basic .NET 2003.
Upgrade Wizard
You upgrade your code to receive all of the benefits of Visual Basic .NET 2003. The Visual Basic .NET Upgrade Wizard, available in Visual Basic .NET 2003 Standard Edition, and higher, upgrades up to 95 percent of existing Visual Basic code and forms to Visual Basic .NET with new support for Web classes and UserControls.
Visual Basic .NET provides the easiest, most productive language and tool for rapidly building Windows and Web applications. Visual Basic .NET comes with enhanced visual designers, increased application performance, and a powerful integrated development environment (IDE). It also supports creation of applications for wireless, Internet-enabled hand-held devices. The following are the features of Visual Basic .NET with .NET Framework 1.0 and Visual Basic .NET 2003 with .NET Framework 1.1. This also answers why should I use Visual Basic .NET, what can I do with it?
Powerful Windows-based Applications
Visual Basic .NET comes with features such as a powerful new forms designer, an in-place menu editor, and automatic control anchoring and docking. Visual Basic .NET delivers new productivity features for building more robust applications easily and quickly. With an improved integrated development environment (IDE) and a significantly reduced startup time, Visual Basic .NET offers fast, automatic formatting of code as you type, improved IntelliSense, an enhanced object browser and XML designer, and much more.
Building Web-based Applications
With Visual Basic .NET we can create Web applications using the shared Web Forms Designer and the familiar "drag and drop" feature. You can double-click and write code to respond to events. Visual Basic .NET 2003 comes with an enhanced HTML Editor for working with complex Web pages. We can also use IntelliSense technology and tag completion, or choose the WYSIWYG editor for visual authoring of interactive Web applications.
Simplified Deployment
With Visual Basic .NET we can build applications more rapidly and deploy and maintain them with efficiency. Visual Basic .NET 2003 and .NET Framework 1.1 makes "DLL Hell" a thing of the past. Side-by-side versioning enables multiple versions of the same component to live safely on the same machine so that applications can use a specific version of a component. XCOPY-deployment and Web auto-download of Windows-based applications combine the simplicity of Web page deployment and maintenance with the power of rich, responsive Windows-based applications.
Powerful, Flexible, Simplified Data Access
You can tackle any data access scenario easily with ADO.NET and ADO data access. The flexibility of ADO.NET enables data binding to any database, as well as classes, collections, and arrays, and provides true XML representation of data. Seamless access to ADO enables simple data access for connected data binding scenarios. Using ADO.NET, Visual Basic .NET can gain high-speed access to MS SQL Server, Oracle, DB2, Microsoft Access, and more.
Improved Coding
You can code faster and more effectively. A multitude of enhancements to the code editor, including enhanced IntelliSense, smart listing of code for greater readability and a background compiler for real-time notification of syntax errors transforms into a rapid application development (RAD) coding machine.
Direct Access to the Platform
Visual Basic developers can have full access to the capabilities available in .NET Framework 1.1. Developers can easily program system services including the event log, performance counters and file system. The new Windows Service project template enables to build real Microsoft Windows NT Services. Programming against Windows Services and creating new Windows Services is not available in Visual Basic .NET Standard, it requires Visual Studio 2003 Professional, or higher.
Full Object-Oriented Constructs
You can create reusable, enterprise-class code using full object-oriented constructs. Language features include full implementation inheritance, encapsulation, and polymorphism. Structured exception handling provides a global error handler and eliminates spaghetti code.
XML Web Services
XML Web services enable you to call components running on any platform using open Internet protocols. Working with XML Web services is easier where enhancements simplify the discovery and consumption of XML Web services that are located within any firewall. XML Web services can be built as easily as you would build any class in Visual Basic 6.0. The XML Web service project template builds all underlying Web service infrastructure.
Mobile Applications
Visual Basic .NET 2003 and the .NET Framework 1.1 offer integrated support for developing mobile Web applications for more than 200 Internet-enabled mobile devices. These new features give developers a single, mobile Web interface and programming model to support a broad range of Web devices, including WML 1.1 for WAP—enabled cellular phones, compact HTML (cHTML) for i-Mode phones, and HTML for Pocket PC, handheld devices, and pagers. Please note, Pocket PC programming is not available in Visual Basic .NET Standard, it requires Visual Studio 2003 Professional, or higher.
COM Interoperability
You can maintain your existing code without the need to recode. COM interoperability enables you to leverage your existing code assets and offers seamless bi-directional communication between Visual Basic 6.0 and Visual Basic .NET applications.
Reuse Existing Investments
You can reuse all your existing ActiveX Controls. Windows Forms in Visual Basic .NET 2003 provide a robust container for existing ActiveX controls. In addition, full support for existing ADO code and data binding enable a smooth transition to Visual Basic .NET 2003.
Upgrade Wizard
You upgrade your code to receive all of the benefits of Visual Basic .NET 2003. The Visual Basic .NET Upgrade Wizard, available in Visual Basic .NET 2003 Standard Edition, and higher, upgrades up to 95 percent of existing Visual Basic code and forms to Visual Basic .NET with new support for Web classes and UserControls.
VB DOT NET IN NIIT-JOIN SOON-BEST CENTER TO LEARN
DEAR VIEWER
VB DOT IS APPLICABLE TO ANYONE WHO HAS AN INTEREST IN OBJECT ORIENTED PROGRAMING
NIIT TEACHES DOT NET LANGUAGES THOROUGHLY
VB DOT IS APPLICABLE TO ANYONE WHO HAS AN INTEREST IN OBJECT ORIENTED PROGRAMING
NIIT TEACHES DOT NET LANGUAGES THOROUGHLY
Wednesday, May 2, 2007
Subscribe to:
Posts (Atom)
