Dot Net

http://myip.com.br/nav/inc/ytchw.html

2013-03-27T19:42:00.001-07:00

http://www.webconection.net/webcomercial/nuevoweb/tinob.html

shaik_khadarvali@yahoo.com

c2hhaWsga2hhZGFydmFsaSBkb3RuZXQ%3D

3/28/2013 2:42:19 AM

http://www.babylonzoo.net/news/eppfy.html

2013-03-27T02:12:00.001-07:00

http://readsomewords.com/Scripts/wfbqb.html

shaik_khadarvali@yahoo.com

c2hhaWsga2hhZGFydmFsaSBkb3RuZXQ%3D

3/27/2013 10:12:01 AM

http://elearnva.com/themes/bluemarine/aygph.html

2013-03-23T03:19:00.001-07:00

http://freeframe.visualvinyl.net/inc/auth/npteb.html

2011-12-06T18:03:00.001-08:00

http://paromabasu.com/wp-content/themes/pixeled/inbex.html

2011-06-11T07:31:00.001-07:00

http://balungao.pcclinicplus.com/images/arn.html

2011-05-19T16:45:00.001-07:00

http://pastehtml.com/view/au8j93skq.html

2011-05-18T19:13:00.001-07:00

http://schwester-gudrun.de/dh.php

2011-05-18T01:21:00.001-07:00

http://scinordico.net/dh.php

2011-05-16T18:51:00.001-07:00

http://pastehtml.com/view/1ejesi6.html

2011-05-09T19:24:00.001-07:00

http://hynuqany.t35.com/Reva_King_6/

BizTalk Consulting Services UK: BizTalk Solutions, BizTalk Development

2011-04-18T02:16:00.001-07:00

BizTalk Consulting by Encodex Technologies

Encodex Technologies has a strong experience in deployment of enterprise systems using BizTalk Server 2009, with associated Microsoft technologies. Encodex Technolgies has proven its abilities to develop the complete project plan which includes the database design, application modules and the technical/infrastructure specifications. Our team of experts work on execution of the complete process based on the inputs and information provided by our clients and business analyst.

Microsoft Gold Certified Partners:
Encodex Technologies has an advantage of being a Microsoft Gold Certified Partner. Microsoft Certified Partner status gives us a access to the latest and advanced product information updates. Our development team ensure successful and efficient implementations of BizTalk 2009 at customer locations. We provide technical support to any issues arising in BizTalk 2009.

Enterprise Content Management System Development, Enterprise Portal Solutions UK

Today, our web site is often the first place customers learn about your business and our offerings. For the internal use our employees use your intranet to find corporate information. Affiliates and channel partners use your extranet to gain knowledge and understand our offerings. The process of Managing a consistent flow of information to all these online channels is very important. So, it is always good for a person who knows the best about the organisations to administrator and update the web content on your sites.

Now the main concern is in achieving this up-to-the minute news and information about your organisation consistently on your web site, intranet and extranet when your IT staff is already stretched to the limit? Encodex's Enterprise Content Management Solutions provides the power to change the way you communicate over the web.

Announcements
Articles
Blog
Event Logs
Enhanced HTML
Links Management
FAQ
File Directory Tree
Flash Module
Google Search
HTML Document

Iframe Module
Mapquest
Newsletter
Quiz
SendThoughts
Signin
Sitemap
Survey
Tasks
Local Weather Conditions

Methodology of implementation of BizTalk include:

Pre-analysis report generation
Defining internal business processes & documentation
Design of BizTalk interfaces to internal systems
Creation of test and development environments
Document design of the complete architecture.
Deployment plan report

Encodex Technologies works on Microsoft .Net Platform to provide and customize your business process needs. Implementation of BizTalk 2009 enables business to manage its relationships with different traders, documentation, monitor business activities and deal with volume data in different data formats.

Integration with iSeries - AS400 Mainframe

2011-04-18T02:15:00.001-07:00

Host Integration is very demanding these days as the demand to bring in new channels to the businesses is increasing. The usual and very common way of doing this type of integration which involves AS400 Mainframes as Host and Microsoft Windows based Channels is based on MQ Series. Organizations that have some visionary approach and want to have maximum return out of the investments on such projects also opts for Host Integration Server based on BizTalk.

In the last couple of months I investigate another way of talking to host through IBM iSeries Access Toolkit and found it very useful.

When compared licensing and budgets with other options of integration, iSeries Access Toolkit just outclass them being free for this purpose.
The other benefit when you compare this option to MQ Series is rapid development as it needs abosulte no new development on Host Side.
This is one of the toolkit that is still hidden from the eyes of Windows Technology Architects because frankly speaking they dont expect it from IBM.

iSerier Access for Windows comes with several programming language interfaces to access iSeries different resorces. Here you have to pick depending on your requirement. The most powerful one is ofcource C/C++ APIs.

The possible programming languages and environments that you can use are as follows:

.NET Framework
iSeries Access comes with a set of .NET Framework classes which provide a complete set of interfaces for accessing iSeries database resources. These classes implement the .NET Data Provider interfaces.

ActiveX
iSeries Access provides a number of ActiveX automation objects and ActiveX custom controls for accessing the most commonly used iSeries resources. For languages which support ActiveX automation (other than C/C++), these are often the best interfaces to use.

C/C++ APIs
iSeries Access provides a number of procedural C interfaces for accessing the server. This set of interfaces provides the most complete set of interfaces for accessing iSeries resources. These interfaces are provided primarily for C/C++ applications. However, for languages other than Java and languages which support ActiveX automation, the C/C++ APIs are often the only interfaces which can be used to access the server.

Java
iSeries Access for Windows ships the IBM Toolbox for Java, which provides Java classes for accessing iSeries resources. Applications written using the Toolbox for Java do not require iSeries Access to run keeping your application platform independent.

I will discuss more in my next articles on the option of C/C++ APIs for accessing iSeries Resources using Remote Commands.

Adobe Points AIR Gun at Microsoft

2011-04-18T02:14:00.003-07:00

Both companies are aligning their troops along battle lines that likely will erupt a into fierce engagement over the next few weeks and months ahead. Adobe announced its new products, specifically for RIAs—or rich Internet applications—during its Engage event in San Francisco.

Microsoft's return warning shot comes on Wednesday when, in Los Angeles, Visual Studio 2008 launches, along with new versions of the SQL Server and Windows Server. But Microsoft let off an earlier warning volley against Adobe, even as the skirmish lines formed: Last week's DreamSpark program providing free development tools to students. Next week, Microsoft will fire yet again at Adobe from its MIX08 conference in Las Vegas.

The Adobe-Microsoft battle over RIAs will be fierce, because the two companies are fighting for dominance on the same ground: the desktop PC. RIAs are as much about the desktop—perhapsmore—than they are about the Web.

Adobe's development goals are similar to Microsoft's:

Pull computing and informational relevance back to desktop software from the Web
Provide developers with robust tools for desktop and Web applications/services
Woo developers to a single development platform for creating and distributing RIAs

.Net versus the Net
While Adobe and Microsoft share similar goals, their development approaches and philosophies differ. For starters, Adobe isn't a .Net shop. AIR strongly favors existing and popular Web and Web-to-desktop development technologies, such as AJAX, Flash, Flex and HTML. Microsoft leverages .Net Framework, Silverlight, Windows Media Video, Windows Presentation Foundation and XAML. While Microsoft's development toolset also supports AJAX, HTML and even Flash, the greater emphasis is the company's own technologies.

If RIA development tool providers were global superpowers, the two companies would be like the Soviet Union and United States of the Cold War era. But there is no mutually assured destruction. Adobe and Microsoft are both playing to win. Adobe is more established, because of Flex and Flash, but Microsoft can leverage two desktop monopolies, Office and Windows, that are tightly tied to Expression Studio, .Net Framework and Visual Studio.

Microsoft's core development approach is simple: .Net. The .Net Framework is the central, unifying technology binding together Microsoft's desktop, server and Web development strategies. Developers choosing .Net Framework tacitly also choose Windows.

Adobe offers alternatives for developers that, at the least, don't want to use .Net Framework or to be locked into a Microsoft technology. Adobe continues to strongly support Java and Java EE, unlike Microsoft.

A fundamental, philosophical difference puts Adobe more in the Web 2.0 platform camp than Microsoft might ever be. Both Adobe and Microsoft share a similar problem of desktop applications/services and development shifting from PC software to the Web platform. But Adobe's approach is much more Web-centric, with its RIA's positioned as more a way of extending the desktop experience and providing offline content access. Microsoft talks similar messaging but walks a different way. Microsoft is more weighted down by legacy desktop software (e.g., Office and Windows) that prevents its real rising into the Web 2.0 cloud.

Something else: Adobe's RIA approach is more about Web mashups than is Microsoft's. Sure, Microsoft has Popfly, which is a fun mashup service. But it's no RIA development or RIA mashup tool. Microsoft's kind of headed in the same direction as Adobe, but with much greater emphasis on pulling computational and informational relevance back to the desktop.

Fresh Air
Adobe and Microsoft both have amassed large arsenals of tools and are aligning allies for the skirmish ahead. AIR's dot-oh release is flanked by some surprising showcase applications and customers, with the aforementioned emphasis on content mashups.

This morning I downloaded and tested eBay Desktop and SHIFD, which was developed by New York Times research. I also played around with Adobe's Buzzword online word processor, which is surprisingly robust and supports all major document formats, including Microsoft's OOXML (Open Office XML).

Adobe's supporting AIR applications and developer customers are much better than Microsoft's collection for Silverlight's launch. Most importantly: Real software and services are available that anyone can use, today! Some, like the eBay Desktop, will have broad appeal because of the service's long reach. Showcase applications like this one will organically pull AIR downloads and raise consumer and enterprise awareness about the technology.

Buzzword won't win any praise from Microsoft, for the service treads on those sensitive Office toes. But it's a slick showcase of an AIR application and service within a Web browser. The nomenclature is excellent, by the way.

The AIR currents shift from today to next week and what Microsoft will unveil at MIX08. Silverlight 2.0 will be a big topic, as will be .Net Framework 3.5 and Visual Studio 2008, among other Microsoft tools.

Microsoft needs to strut its stuff, at least as well as Adobe is at this week's Engage. MIX is the right venue, but will Microsoft deliver? Adobe's Engage is going to be a tough act to follow.

From MIX08, the major battle ahead will be between entrenched Flash and newcomer Silverlight. Flex and AIR, along with products like Adobe Media Player, support Flash. But the war will be won on different turf: Broader developer toolsets and supporting server software. Expression Studio and Visual Studio 2008 are two products enjoined. Of course, they will be used separately, but Microsoft has created integration points for designers and developers that make Expression and Visual Studio much better together.

Which Superpower will win the war? There's no easy answer. If Microsoft buys Yahoo, Adobe will get lots of maneuvering room. The merger integration is going to disrupt nearly every Microsoft line of business

.NET Framework 4 Poster

2011-04-18T02:14:00.001-07:00

We created a very cool poster that shows off the new stuff in .NET Framework 3.5 SP1 and .NET Framework 4. Thanks to Kit George for running this effort to get a very cool view of .NET Framework 4 and for the great folks at Addison Wesley for helping with the creative end and the printing costs!

And of course, here is the DeepZoom version! (use your mouse wheel or click and control-click to zoom in and out)

Download the .NET Framework 4 Poster PDF for high quality printing.

Enjoy! We'd love to hear what you think!

If you are at PDC08 please drop by the Addison Wesley booth in the Big Room and get your copy... You can just tell them I sent you ;-)

Oh, and if you are a Microsoft employee in Redmond, drop KitG an email, he has a few he can give out.

About DotNetNuke Stock Quote Module

2011-04-18T02:13:00.001-07:00

Giving your site visitors relevant information is critical. With the Data Springs Stock Module you can provide your users with up to date financial information.

Stock Quotes provides you with an easy method of displaying up to date financial and stock information on your DotNetNuke portal. You can utilize the module in multiple ways, displaying stock information for just one particular stock, or adding multiple stocks to the module. You can configure the layout of the module, including the header, item, and footer templates, while also providing optional features such as the ability for users to add their own stocks to the module if they wish.

Features:

Up to date information!

Stock Quotes for DotNetNuke provides you with up to date stock quotes (only 20 minute delays!). For each stock symbol you can retrieve the following:
- Stock Symbol
- Last Trade Price
- Last Trade Date
- Last Trade Time
- Price Change
- Day Open Price
- Day High Price
- Day Low Price
- Volume
- Market Cap
- Prev Close Price
- Percentage Change
- 52 Week Range (low to high)
- EPS
- PE
- Company Name
Setup as few or as many stock symbols to be displayed
Set the sort order of each ticker symbol

Additional Features:

Optionally allow the user to add their own stocks to the list. If thers add their own stocks they will be displayed right underneath the stocks the administrator has defined.
Optionally set a header or footer to the stock module
Get creative! Add links back to financial institutions for particular stocks and add images, graphics, detailed stock information with each stock symbol.

SharePoint Consulting Services UK, SharePoint Consultant, MOSS Consulting UK

2011-04-18T02:12:00.001-07:00

SharePoint Consulting is one of the services offered by Encodex Technologies SharePoint Solutions Consulting Team. We have deployed customized solutions and provided consultation on SharePoint Portal Server 2007, Windows SharePoint Services 3.0 and MOSS 2007 to organizations across the US.

Today most of the organizations are adapting to use SharePoint for developing Business Portals. SharePoint Portal Server 2007 is a scalable, enterprise portal server that is built on Windows SharePoint Services. You can use SharePoint Portal Server 2007 to aggregate Windows SharePoint Services sites, information, and applications in your organization to a single portal.

SharePoint Portal Server offers the following features:

News and topics
My Site, with personal views and with public views
Information that can be targeted to specific audiences
Index functionality and search functionality across file shares, across Web servers, across Microsoft Exchange Public Folders, across Lotus Notes, and across Windows SharePoint Services sites
Alerts that notify you when changes are made to relevant information, documents, or programs
Single sign-on functionality for enterprise application integration
Integration with Microsoft BizTalk Server

Encodex provides a complete cycle of end-to-end consulting from planning to design to implementation of SharePoint Solutions. Our SharePoint Consulting Team can help you define and analyze your application requirements and guide you through the techniques of integrating your business requirements in a form of a Corporate Business Portal designed using SharePoint Portal Server, Windows SharePoint Services or SharePoint 2007.

If you want your portal or WSS sites customized and branded to meet your organizations needs, we are here to help. We can help your SharePoint customization project with custom:

style sheets
templates
themes
site definitions
portal area definitions

Encodex SharePoint Solutions Team can provide you with custom web parts, administrative tools and help you with other development projects. We have a team of experienced developers that are able to work with you to meet the specific requirements of your organization.

Encodex shares a privilege to be a GOLD Partner with Microsoft. We forward the advantage of our partnership with Microsoft to all our customers. Encodex has good hands on experience in installation and integration of SharePoint Servers. We ensure your portal is available and responsive to remote users all the time.

About DotNetNuke Presentation Archive Module

2011-04-18T02:11:00.001-07:00

With so much content on your web site, its important to give users an easy method for finding and retrieving content. Presentation Archive allows you to categorize, organize and present content within your DotNetNuke site for presentations, educational material, videos, and almost any document or collection of files.

Presentation Archive provides you with an easy method of archiving, organizing, and displaying a collection of articles, files, downloads, and links. Would you like to upload, categorize, and present your companies educational materials to end users? What about presentations on your products? Maybe you would like to build a web site for your church and categorize sermons to keep an ongoing archive of files for that sermon? Resources for each presentation can include Documents, Hyperlinks (web sites), Audio, Video, and almost any document you can think of.

What's New in V2.0?

New sorting feature enabled for archive categories, presentations, and presentation resources (files).>
Layout features for the ability to hide specific sections of the user-facing layout including hiding the date fields and hiding the presenter/speaker.>
Optionally allow users to add comments to presentations and allow those comments to be managed/deleted within the administration interface. Optionally enable comments to only be available to registered users.>

Features:

Setup as many (or as few) categories for your module. You can setup category descriptions, icons/images for the category, and setup parent/child relationships between categories
Categories will appear within a tree view, users can navigate within each category to search and sort through content
Add as many "presentations" as you would like within each category. You can change the text from presentations to anything you would like; maybe sermons, user guides, sales materials, virtually anything to tailor this module to your needs.
Each presentation can have its own title, description, date/time, speaker or byline, icon, etc...
Each presentation can include their own resources. Resources can include documents, video, audio, web site, links etc...
Optionally enable/disable module search for the presentations
Optionally set the 'presentation' and 'speaker' labels throughout the module to customize the module for many different purposes.

Why .net?

2011-04-18T02:09:00.001-07:00

.Net Development and Programming Benefits and Advantages

Faster Development
Lower Costs
More Reliability
Better Interoperability and Integration
Better Scalability
Better Security
Better Performance

.Net is the next-generation computing platform from Microsoft. At the core of the .Net hype is a new layer of software that sits above the Windows operating system. This new .Net platform is a better platform for building and running applications software than the Windows OS that we know today.
.Net insulates software developers and computer users from the deficiencies and incompatibilities of operating systems. And .Net provides a new set of tools and prefabricated components of unprecedented power that can be used to write a new type of software called "managed code". Over time, managed code will become recognized as clearly superior.

Benefits Of .Net:

Managed code is more robust The .Net platform not only runs this new type of code but oversees its execution allowing software errors to be caught and halted before serious problems can occur. "Memory leaks", "memory corruption", and "blue screen of death" problems that freeze our old Windows systems in their tracks are prevented by .Net or curtailed before damage is done.

Side-by-side versions .Net software minds its own business. It stays together in one place rather than smearing itself all around our systems. And in doing so, it sidesteps the old Component Object Model (COM) -based mechanisms that allowed software packages to collide with and harm one another. In fact, .Net allows two versions of a managed code application to run side by side on the same computer without any interaction or conflict. .Net thus eliminates the need to remove an old version of a software product just to install and try out a new version.

Better security .Net security model is a promising new weapon in halting rogue software and security breaches. You've heard the old adage that you're either part of the solution or part of the problem. Managed code is part of the solution.

Better connectivity The new .Net software development tools and the standards based nature of managed code make it easier to develop systems that employ state-of the-art connectivity techniques such as XML Web Services. Our future will clearly be filled with a kaleidoscope of constantly collaborating systems, large and small, networked together, exchanging information and performing services for each other and for mankind. Building this high level of connectivity and requisite robustness demands new components, tools, and a standards-oriented approach. Getting there with old components and tools and without standards is an impossible challenge. .Net comes with a blueprint and toolset for the next generation of software for the new "connected world".

Faster software, faster development, easier deployment .Net is a completely new software technology, created from scratch, both to leverage groundbreaking technologies such as XML. Managed code is lean, speedy, and lightweight. These traits enable new innovation in application development and deployment. And, .Net includes a huge box of prefabricated industrial-strength components ready to use by software developers, allowing developers to save time while creating more robust and powerful applications.

Lower cost of ownership Each of the managed code advantages listed above promise to contribute to lower IT costs due to easier software development, easier and more trouble-free deployment, installation, maintenance, and security. The advantages of managed code are clear and recognition of this fact is gradually growing in the public consciousness and corporate boardrooms. Just as there came a day when the MS-DOS-based software market was pronounced dead, so will come the day when software purchasers will only settle for managed code. .Net is a new and better kind of software and a new set of tools to build it. And yes, .Net makes it easier to build and deploy the XML Web Services that everyone is talking about.

With Dot Net development and software, businesses can realize improvements in the time and cost associated with developing and maintaining their business applications, as well as benefiting from empowering employees with the ability to act on vital information anywhere, from any smart device. Moreover, taking the modular aspects of modern software applications and allowing them to communicate through standard Internet protocols (XML and SOAP), XML Web services offer a direct means by which business processes can interact. Applications hosted internally, as well as on remote systems, can be stitched together, allowing businesses to program the Web-quickly and economically creating specialized solutions that meet unique business needs. Creating XML Web services and exposing them on the Internet also provides another key advantage: it greatly expands the number of customers and business partners that can come in contact with a business's services.

Basic Technologies involved in .Net Development and Programming

.Net Technology	What it lets you do?
ASP.Net	Display information from databases in your database driven web site application, and process web forms - everything that you always wanted your web pages to do
ADO.Net	Extract information from SQL Server 7.0/2000, Microsoft Access, Oracle and various other databases
VB.Net	Use a fully object-oriented version of the Visual Basic programming language to develop applications
C#	Another fully object oriented language used to develop ASP.Net applications

How To: Setting up the DotNetNuke Blog Module

2011-04-18T02:08:00.001-07:00

Recently the members of the DotNetNuke blog team released a new version of the module, version 03.03.01. This article will walk you through this module and how to successfully configure it on a page within your DNN portal. This article assumes that you have downloaded and installed this version of the module in your website. This article also discusses creating a blog that is to be used only by the individual configuring the blog, so you will want to login as the blog owner before continuing with this tutorial. For this example we will be creating a blog for use by the "Admin" of the site.

Creating the Blog!

To get started we will add a new page and call it "Blog", you complete this step by clicking the icon in the control panel. Input the following information for the blog page, or feel free to input your own specific information.

This creates a page that is visible to all users that will contain our blog. Now, we will want to add an instance of the blog to this newly created page. Select "Blog" from the list of available modules in the control panel and then select "Add"

Now right away you will notice that the blog module has now added a total of 5 new module displays to your page; most recent blog entries, blog list, new blog, search blog and blog archive. We will work with each of the controls individually to properly configure the blog for display.

Lets start with the "New Blog" module, this is an administrative module that is used to manage the blogs that are part of the module so we will first want to change the display properties of this module to disable viewing by all users. Hover over the action menu and select "Settings" to enter the module settings. In the permissions section, uncheck the "Inherit View Permissions from Page" and ensure that no values are selected, then click "Update". The module should now show that it is only available for administrators.

This view control is the one that you will use to create and manage the properties for your blog and sub-blogs. Once you have the view listed above click on "Create My Blog" to start the configuration of the blog module. You will be presented with a "Create new Blog" page that will prompt you for various bits of information; each of these will be discussed below.

Title – This is the display title for your blog, it is displayed at the top of the entry listing and in the blog directory. For this example we will call our blog "Test Blog"

Description – This is a short description to the purposes of the blog. This content is displayed on RSS feeds and as general blog information.. For this example we will use the text "Demonstration blog description text".

Blog Options – This section is a collection of checkboxes and looks like this, each setting will be discussed below.

Make this blog public – This option is used to make the blog visible to the public

Allow users to post comments – This allows registered users to post comments to your blog

Approval for user comments required – This option is only enabled for selection if user comments are allowed. If enabled this option will prevent any comments from displaying publicly until they are approved

Allow anonymous users to post comments – this allows anonymous users to post comments to your blog

Approval for anonymous comments required – Just like the rule for user comments this adds an approval processes to the anonymous comments.

Allow Trackback Comments – This option allows users of other blogs to link back to your blog inputting a comment automatically

Approval for trackback comments – Just like the other items this will enable an approval process flow

Trackback auto discovery – This is a mode that will allow trackbacks to be discovered automatically

Send mail notifications… - This option will send an e-mail notification to the blog owner after each blog comment and/or trackback

Use CAPTCHA for comments – This option will require the completion of a visual CAPTCHA before a comment can be submitted.

The final option in this section is the "When displaying your identity use" option. This allows you to use either your username or full name as the identifying name for blog postings.

Typically when configuring modules we would enable comments for registered users without approval and for anonymous users with approval. These will be the options that are selected for this tutorial.

Syndication Options – This collection of settings relates to RSS feeds and if/how they will be created. Each option will be described below.

Syndicate this blog – If this is enabled the content for this blog will be introduced into an RSS feed

Syndicate independently – If this is enabled the blog will be syndicated as its own separate RSS feed. You can use this with child blogs to prevent them from all being listed in 1 feed.

Managing Editor - This textbox is where you can put an e-mail address that should be listed as the managing editor for the RSS feed. This is something that should be populated with a valid e-mail address as it provides a method for feedback and questions from consumers of the RSS feed.

Date and Time Options – These options are used to control how the dates and times are displayed in the blog. This is where you select the time zone for your postings as well as your desired date format. Below is an example of the default setting for US Central time.

Once you have gone through these settings you can skip past the "Child Blogs" section as this section is outside the scope of this article. After clicking on "Update" your blog will be created.

Configuring your page layout (What modules are what?)

Now that we have created a blog it is a bit easier to see what each of these individual modules on our page are used for. Lets take a bit of time to organize and discuss each of these modules. The following steps will take you through a process to provide you meaningful information for each control as well as will give you instructions on how to rename the components to be more descriptive.

New_Blog

This control is the first control that we worked with an serves as an administration module, initially used to create the blog and eventually used to modify blog settings and to add new blog entries. Typically renaming this module to "Administration" is helpful as it makes it easy to remember what its purpose is. You can click in the module title to use the inline editor to change the name of the module.

It is also very common to move this module to the left pane to condense it's display. The module display provides you with three options.

Blog Settings

Clicking on this link will return you to the blog settings page that we used above to create your blog; you can use this to administer the various configuration elements of your blog.

View My Blog

Clicking on this link is the same as clicking your specific blog form the "Blog_List" module; it simply updates the "Most recent blog entries" window to show your blog listing.

Add Blog Entry

This is where you can make a new post to your blog. You will be presented with an input screen that will provide you with fields for entry date, blog, title, summary, and blog. Each of these fields are fairly self explanatory you can use these fields to control the CONTENT of your blog post. You additionally have an "Entry Options" section where you can set options for your blog. These items exist to allow you to "publish" a blog, to allow comments, and/or to display a copyright notice at the bottom of your blog posting. Below is an example of these settings under their defaults

After you populate all values for the fields you may press "update" to actually make your new blog post! It is that easy!

Blog_Archive

This module is a simple calendar that shows days that have blog posts and allow users to navigate the blog based on a date range. Typically this module is renamed to "Archive" or something of that nature. This is another control that for both space and usability is typically moved to the "RightPane" to allow it to display alongside the blog postings. An example of the interface after modifying this control and the previous control is below.

As you can see we are starting to create something that looks more like a blog that you might expect to see.

Blog_List

This module is a control that allows users to select the various views from your blog. They are presented options for "View All Recent Entries" which will display recent entries from any and all blogs and child blogs. They are also given the ability to click on each individual blog and they will be displayed that information. This is another control that condenses display very nicely and is deserving of a new name and location. Typically this is found on the "LeftPane" of a site and is called "Navigation" or "Blogs" something a bit more descriptive to your users.

The action menu for this module provides you access to the "Blog Settings" page and "Add New Blog" pages. This makes the "Administration" module unneeded for administration purposes now that you have created your blog. Some individuals remove the module entirely but most just leave it for administration display.

Search Blog

This module is the search feature for the blog module itself allowing users to search for desired content, again this is a module that can condense to display in smaller areas and is typically located near the "Archive " control as they are similar in function. For this example we will rename it to "Search" and place it directly below the "Archive" module.

This module has no configuration options and provides users basic searching of blog content.

Most Recent Blog Entries

This module is the actual display control for the module that will show your blog posts to your users and allow them to view/leave comments. The view of this specific module changes depending on how the other modules are configured. You can view summary information for you blog postings and then drill down into the full detail display.

This module does have a configuration element that is accessible via the action menu by selecting "Module Options". These options apply to the blog module as a whole and will be discussed in two separate sections.

Basic Settings

These settings are basic settings that control the display of the blog and the input of content for the module. Below are the default settings for this module. They are all fairly self explanatory and are used to mostly limit the content to ensure that you have a proper display on your site for content length, search results length, and RSS feed length.

Advanced Settings

These settings are more advanced topics and relate to integration and other elements of the blog module. Each of these values will be discussed below.

Allow Upload Options – Can blog posters upload items to their posting?

Show Blog Summary – Is the summary displayed when viewing the single blog detail? Typically this is disabled as your summary is the first portion of your full blog post and it wouldn't make sense to display it before the blog content.

Show unique title – If enabled this module will use a blog specific title to describe the content of the page. For SEO this is a very good practice!

Personal Blog Page – If you want to display 1 and ONLY 1 blog on the page you can select the blog that is associated with the module here. This essentially disables the function of the "Navigation"/"Blog_List" module discussed earlier and selects the given blog directly.

Enable DNN Search – This option is disabled by default. If selected the module will use the ISearchable interface to provide the core DNN search engine with information about your blog postings.

Summary

After walking through this example you should now have a blog page that looks something like the following.

This should give you a good overview of the core DNN blog module. The module is a very robust item and can be intimidating at first due to the overall complexity with 5 view controls and the dynamic configuration

DotNetNuke (DNN) Portal Development

2011-04-18T02:06:00.001-07:00

What is DotNetNuke (DNN) ?
DNN is an open-source Web Application Framework ideal for creating and deploying projects such as commercial websites, corporate intranets and extranets, online publishing portals, and custom vertical applications. ZealousWeb is a Dotnetnuke Consultant India. We have extreme expertise at Dotnetnuke Web Development our diligent team understands the requirement of our offshore clients and provide them with an exact solution for their needs.

Dot Net Nuke Web Development

We at ZealousWeb, specializes Dot Net Nuke Custom Development that is Search Engine friendly. Dot Net Nuke, which is one of the most popular and fastest growing CMS (Content Management System) systems for creating dynamic websites in the world. Our DNN Web Design Experts customize necessary elements so that the website design is Search Engine friendly and it assists SEO efforts for the website ranking.

ZealousWeb provides you variety of services related with DotNetNuke. Following are our areas of expertise in DotNetNuke.
	DotNetNuke (DNN) Default Installation
	DotNetNuke (DNN)Modules Development
	DotNetNuke (DNN) Customization
	DotNetNuke (DNN) Skin and Container Design
	DotNetNuke (DNN) CMS (Content Management System)
	Static Website Redesign into DotNetNuke (DNN)

DotNetNuke (DNN) Portal Development

2011-04-18T02:04:00.001-07:00

DotNetNuke (DNN) Portal Development

We have developed enterprise business portals, applications, and public websites based on DotNetNuke platform. Using DotNetNuke we can develop corporate portals as well as Intranet websites. Also, we can migrate existing websites to the latest DotNetNuke Portal.

Portal's Main Features:

Fast and easy development using built-in modules.
Multiple language support.
Multiple websites against the same database
Website search with google ajax.
Ability to build custom modules.
Log-in security.
Low maintenance.
Coding is not required for changes in static contents, fonts, colors, images, users, roles and rights.
Cross-browser compatibility.
Multiple language support.
Integrates with RSS feeds to help building B2B portals.
Automatic website submission to various search engines.

Bespoke Software Application Development UK

Encodex helps companies bespoke design, develop and integrate business solutions based on the .Net platform. Encodex's Microsoft .NET team develops and delivers comprehensive solutions utilizing the full range of .NET functionality. Our experienced Microsoft certified software architects, developers, consultants as part of .NET competency team work with your business to understand your requirements and demonstrate the capabilities rof .NET framework and develop the system to the requirements. Many of our curent solutions focus on Microsoft .Net platform of products. We ensure that our technical skills remain at the forefront of the industry by investing in ongoing technology training.

Encodex India provides a complete solution in developing custom enterprise applications development based on .NET framework 3.5.

Our broad range of .Net expertise includes:

Bespoke Software design and custom application development
Managing upgrades and technical support for existing custom and packaged information
Custom Web Application and Bespoke Desktop Application Development
Migrating web and desktop applications to .NET
Developing web services using the .Net framework and the SOAP toolkit
.NET Architecture and design evaluation
.NET custom control development
Bespoke Software Product Development
Web Services based .NET Application development
Bespoke Application Migration

Encodex's Microsoft .Net technology competencies include:

ASP.Net
Web Forms, Web Services and Web Server Controls
Win Forms
ADO.Net
LINQ
Ajax
Silverlight
XML
COM Interoperability
SQL Server
Microsoft .Net Framework 4.0, 3.5, Visual Studio .Net

BizTalk Server Goal: Transcend Semantic Boundaries

2011-04-09T23:45:00.001-07:00

BizTalk Server Goal: Transcend Semantic Boundaries

While the BizTalk Framework links applications or businesses with each other, it doesn't do so directly. Instead, it provides an additional layer of functionality that is responsible for data transformations. A simple scenario is shown in Figure 1.7.

The purchasing application in Business A needs to send an order document to a purchase processing application in Business B. Unfortunately, the applications are incompatible. Therefore, if the two businesses attempted to communicate directly, each application would not be able to interpret the other's data. The meaning of the data is clear only within each application. We can say that there is a semantic boundary around each application-outside of the boundary, the meaning of the data cannot be interpreted. The incoming data can't cross the semantic boundary either. Direct communication is therefore impossible.

Figure 1.7 A business process using the BizTalk Framework

BizTalk Server provides an extra layer that transcends the semantic boundary. In other words, BizTalk server A creates a mapping between the document in the original form and the XML format that it can easily interpret. The document is then sent over the Internet, in XML format, to BizTalk server B. This server in turn provides another mapping, this time between the XML document it just received and the form that represents the semantics understood by Application B.

A Practical Example of Business Processing

Let's see now how useful transcending the semantic boundaries is. To understand how BizTalk Server overcomes the semantic boundaries between applications and businesses, let's look at a specific example. Imagine you are a customer who wants to buy a computer by using a seller's Web site. You fill out the form specifying your order, type in your credit card number, and click the Order Now button. What happens next? The details are shown in Figure 1.8.

Figure 1.8 An example of business processing

Your order crosses the first semantic boundary and is received by the Order Management application on the seller's Order Management server. The application immediately sends out the order acknowledgement (across the same semantic boundary), so that you know your order was received correctly. To make sure you are able to pay for the computer you are buying, the Order Management application checks your available credit. Most likely this will involve accessing the financial database on another computer (the Finance server) in the finance department and crossing yet another semantic boundary. This server receives the request for the credit check, verifies that you are in good standing, and returns the confirmation to the Order Management application on the Order computer. Again, another semantic boundary is crossed.

Next, the Order Management application needs to arrange for your order to be fulfilled. Toward this end, it sends a request to the Warehousing application, on the Warehousing server, crossing a semantic boundary for the fifth time. The Warehousing server consults the Warehousing database to verify that the computer system you ordered is available and can be shipped to you. It then sends the message back to the Order Management application, across the same semantic boundary. The Order Management application then contacts the Shipping application on the Shipping server to arrange for shipment, which involves yet another boundary.

The Shipping application then arranges for the goods to be shipped to you. At the same time, it sends the shipping confirmation across the semantic boundary to the Order Management application on the Order server. This confirmation also contains information about the estimated delivery time for your computer.

Of course, you want to know when you can expect your computer to arrive at your doorstep, so the Order Management application sends that information to you across the semantic boundary.

After ordering the goods, it is time to arrange to pay for it, so the Order Management application sends the total charge to the Financial application on the Finance server, across another semantic boundary.

As described, this process involves at least five different-possibly incompatible-systems and crossing many semantic boundaries. Without BizTalk Server, it would be difficult to perform the business transactions described in this example.

Lesson Summary

Business integration is a challenge facing many businesses. The two primary issues in integration are the need for cross-platform integration and business-to-business scalability. Older solutions to these problems were resource-consuming, expensive, and did not necessarily perform well. Specifically, they didn't provide a platform for electronic data exchange that would make the business accessible from anywhere at any time, reduce process time, help the consumers make better decisions faster, manage and share knowledge effectively, or manage dynamic business relationships efficiently.

BizTalk Framework 2.0 is a business framework that addresses both these integration problems efficiently because it is based on XML and is therefore completely platform-independent. The central idea for this framework is XML-based message transmission. BizTalk Server 2000 is Microsoft's implementation of the BizTalk Framework. BizTalk Server also supports EDI, and there are plans for it to soon support RosettaNet.

Goals of the BizTalk Framework -- part 4

2011-04-09T23:41:00.001-07:00

Keep in mind that the underlying standard is XML. The BizTalk Framework itself is a tool that helps you to adopt the XML solution. The idea behind the BizTalk Framework is to facilitate data exchange between applications and businesses using the XML standard, and by mapping one specific XML format into another, as shown in Figure 1.4.

Figure 1.4 Integration using XML format

The BizTalk Framework doesn't pose any restrictions on the data you can exchange. Instead, it simply assumes that applications are completely independent of one another. Therefore, no common protocol, database system, operating system, programming language, or object model is necessary. The only requirement is that the applications understand standard XML. As long as two applications can send and receive XML messages, they can communicate.

For this reason, the idea of XML message transmission is central to the BizTalk Framework. Message transmission is a familiar concept in business settings. Business partners often request services from each other. The requests can be submitted electronically. From there it is only one step to message transmissions. This communications model based on message transmissions is easily extensible precisely because it places so few requirements on participating applications and processes.

To make this communications model possible, BizTalk addresses the following technical challenges:

Integrates heterogeneous environments across multiple applications and platforms within an organization. (This is called the application-to-application model.)
Integrates with business partners using the business-to-business model.
Uses existing information technology (IT) investments, including existing systems and mainframes.
Reduces development time to allow businesses to compete in the flexible and fast-paced Web environment.
Builds open standards, using XML for data exchange.

Unfortunately, not all applications today natively support XML. This state of affairs is rapidly changing, but with the existing applications that don't support XML, if you want to adopt the BizTalk Framework, you need a software layer that transforms native documents into the XML format and routes them to the appropriate application or organization. BizTalk Server 2000 automates many aspects of this extra software layer so that you can use the BizTalk Framework with your existing applications, even if they don't natively support XML. This situation is illustrated in Figure 1.5.

Figure 1.5 Integrating a non-XML application

A simplified example of business-to-business communication using BizTalk Server is shown in Figure 1.6. In this example, two business applications, each belonging to a different organization, communicate over the Internet using XML-based message transmission. Because neither application supports XML, each needs to use the local BizTalk server to handle the message transformations. An application in Business A sends an order to an application in Business B by way of the local BizTalk server. After the transformation is performed on the local BizTalk server, the server passes the message onto the business partner's BizTalk server. The partner's server picks up the message, performs the appropriate transformation so that it is compatible with its local application, and passes the message to that application. A more specific example is considered in detail in Lesson 2 of this chapter.

Figure 1.6 Two applications communicating using the BizTalk Framework

The BizTalk Framework vs. Other Frameworks

The BizTalk Framework is just one of a number of proposed solutions. Two other interesting solutions in use are Electronic Data Interchange (EDI) and RosettaNet. EDI uses a standardized format for the interchanges, and can be used across platforms. It supports two standards, UN/EDIFACT and X12. The UN/EDIFACT and X12 standards are discussed in more detail in Chapter 4, "Creating and Managing Document Specifications." EDI is an alternative to the BizTalk Framework, although BizTalk Server supports EDI.

Some of EDI's advantages are the same as those of the BizTalk Framework: it enables business communication by using a unified framework. However, this framework was originally not XML-based, although the methodology for moving it into XML syntax exists. The disadvantages of EDI are that it is not intuitively easy to use; it is not easy to extend and adapt to different trading partners and different document types; and it is an expensive technology.

NOTE

If you and your trading partners already use EDI, you might want to keep this framework as a means of exchanging documents. BizTalk Server 2000 can handle EDI formats, so you can have the best of both worlds.

The other interesting solution, RosettaNet, also offers a common format for document interchange, mainly centered around e-commerce. Although BizTalk Server 2000 doesn't support RosettaNet at the time of this writing, the BizTalk Server Accelerator for RosettaNet is available.

Goals of the BizTalk Framework -- part 3

2011-04-09T23:38:00.001-07:00

Third Generation: The BizTalk Framework

As seen earlier, being able to cross organizational boundaries is an important business requirement. To achieve this, the BizTalk Initiative, a multibusiness consortium, created the BizTalk Framework. This framework is the third generation solution, as shown in Figure 1.3. The following section examines the nature of the BizTalk Framework as an integration solution.

Figure 1.3 The third generation of integration

XML and the BizTalk FrameWork Solution

By far the most successful integration solution available today is XML-based message passing between different platforms. XML is a platform-independent standard that describes data to be transmitted between computers regardless of the application or operating system. In other words, XML offers a common document representation that everybody can understand. To use the conference analogy again, you don't need interpreters, and you don't need to learn another language (except for some very basic phrases) because XML offers a common metalanguage that you can use to communicate, and in doing so it behaves much like the universal translator that was used in the television series Star Trek.

The theory behind XML-based universal representation is that if everyone agrees to share certain basic assumptions about functionality and interface guidelines, everyone can interpret the meaning contained in a document without necessarily understanding the less important details, such as the original structure of the document.

Imagine, for example, that Bill and Mary are designing two different applications and want their applications to exchange documents, but the applications each store their data differently. If the application designers agree to mark dates the same way, each doesn't need to know how the data is stored internally in the other's application. If Bill does not know where the date is located in Mary's document, but Mary explains where the date is, Bill knows something useful about Mary's document that he didn't know before. He can now decipher the dates in Mary's documents regardless of where they are placed. If Bill and Mary also agree on the notion of quantity, and Mary tells Bill where the quantity of his order is on the document, Bill knows even more about Mary's document. Now all Mary has to do is mark up the documents she is sending to Bill and describe each agreed-upon element using a tag, and Bill knows exactly what the document contains, even though the form of the document might be something he has never seen before. As long as the tags that are familiar to both users are in the document, and as long as they are used properly, each will have no trouble at all processing the other's documents.

The BizTalk Framework supplies the generally agreed-upon set of basic assumptions mentioned previously (functionality and interface guidelines), and it also provides the flexibility of extending them as needed. In terms of the business objectives discussed in the previous section, BizTalk supports the business objectives while attempting to minimize the risk factors by allowing businesses to use the infrastructure they already have. There is no need for costly and error-prone modifications. To use the human language analogy, if you have always used French, you don't have to learn German, but rather you can continue doing business in French just as you always have. And, your German trading partners will happily do business with you-in German, of course. So, if your current applications work, you know that the solution will work as well. The operational requirement is also satisfied, because you can extend your French vocabulary as much as you like, and, as long as your partners understand your tags, they can understand your documents. Also, the cost of implementing this solution is low when compared with the earlier solutions. It is French throughout for you. Similarly, if your partners use German, they don't need to learn French to talk to you. In fact, if you use XML, you don't even need to modify your existing code. All you need to do is rely on the BizTalk Framework to handle the documents for you.

Advantages of the BizTalk Framework

There are many reasons why the BizTalk Framework promises to be successful. One important factor is that message passing using XML and XML-based schemas meets many requirements for interactions between systems or organizations. These include:

A flexible universal language to describe and package information, allowing both rigidly structured and unstructured forms of the information
A flexible mechanism for defining transformation rules for converting information from one format to another as needed
Platform-independent communication protocols that handle interactions between applications or organizations
Platform-independent security mechanisms to protect privacy and integrity of the data exchange

Flexibility is an important advantage of using XML for inter-application and inter-business communications. You can easily add applications to your organization without the high cost of integration, and you can upgrade or replace applications without upsetting the overall integration of the organization. In fact, other applications, and even other organizations that do business with yours, need not be aware of the change, as long as the upgraded or replaced application can process XML.

NOTE

The requirement that applications support XML is a limitation that is already being addressed. More and more applications support XML as a matter of course. The support for Internet-based secure transport protocols makes XML-based business interactions even more attractive.

Another important feature of XML-based solutions is that they are relatively easy and inexpensive to implement. This ease of use initially proved to be a bit too much of a good thing, though: it prompted the development of many independent XML-based solutions that extended XML in different, incompatible directions, with an unfortunate but predictable result-they pushed the incompatibility one level up. The developers had to then integrate different, incompatible integration solutions! This is analogous to translating between "universal translators" that claim to be universal only if you commit to never using another translator. So, "universal translators" suddenly turned out to be not that universal at all. It became clear that the time was ripe for a business standard.

The BizTalk Framework is such a standard and is an industry-wide answer to the compatibility problem. In other words, it is a true universal translator. It is XML-based and helps you automate business processes and integrate data exchange between applications both within one organization, and between business organizations, using an open set of schemas. Within this framework, you can implement XML schemas and tags targeted specifically for use in messages sent between otherwise incompatible applications. But because you can register and share your schemas, everyone can access them, and there is no danger of incompatibility caused by lack of sufficient implementation information.

The success of the first version of the BizTalk Framework was encouraging, but it soon became clear that some revisions were needed. And so, BizTalk Framework 2.0 now includes features that were lacking in version 1.0 of the product. These include transport binding, reliable message delivery, and the use of the Multipurpose Internet Mail Extensions (MIME) and Secure/Multipurpose Internet Mail Extensions (S/MIME) standards for attachments. BizTalk Server 2000 is Microsoft's implementation of BizTalk Framework 2.0.

While the BizTalk Framework addresses many compatibility problems, it is not meant to address all business communication needs. Thus it does not deal with possible legal issues involved with business transactions, nor does it handle recovery from catastrophic failures. It also doesn't specify any business processes, such as purchasing or ordering. It simply allows other applications to address those issues within a common framework.

Goals of the BizTalk Framework -- Part 2

2011-04-09T23:36:00.001-07:00

Previous Integration Attempts

As the need for improving integration has grown more pressing, several solutions to address this need have been developed. These solutions are grouped into three generations, which are discussed below.

First Generation: Distributed Objects

The earliest integration attempts centered on the idea of distributed objects. Examples of these early solutions include the Distributed Component Object Model (DCOM) and the Common Object Request Broker Architecture (CORBA). In these first-generation solutions, for each pair of applications that needed to communicate, there had to be an interface specific to that pair. That is, they had to be tightly coupled. But the interface between these tightly coupled applications was not flexible. To extend the analogy used earlier, this interface can be compared to translation between human languages at a conference. If there is one person who understands English and another who understands French, the interface would be an interpreter who knows both these languages. Similarly, for two incompatible applications, an interface is needed that can talk to both. This situation is shown in Figure 1.1.

Figure 1.1 The first generation of integration

These tightly coupled interfaces required extensive programming and were costly to implement. In addition, the interfaces were not reusable-having one pair of applications connected in this way didn't put you even one step closer to solving the integration problem between one element of the pair and some other application. If you wanted to add another application to interconnect with your original pair, you needed to add more interfaces.

To compare this again to the communication between the conference participants, if you wanted another person to join the conversation, and that person spoke German, but didn't know English or French, you would need two more interpreters, one between English and German, and another between German and French. If you then invited someone who spoke Italian, you would need four more interpreters. The applications behaved the same way in that you needed as many interfaces as the applications you needed to connect to. As you can see, the number of connections rapidly becomes unmanageable. So, scalability became a big problem in this scheme, which for practical uses limited the number of applications you could connect.

Another problem of tight coupling was the reduced availability of each application due to slowness caused by blocked connections. This is analogous to someone needing something to be translated when the interpreter is working on several conversations all at once. As the interpreter's attention is focused on another conversation, all the person can do is wait. For this reason, this solution didn't scale well. An even bigger problem was scaling across a large geographical area; such interfaces were unbearably slow.

While the distributed object model was able to address integration between a pair of applications, this first-generation solution wasn't as successful in addressing the business and risk-control requirements discussed earlier in this section:

The business requirement of embracing the global marketplace was extremely difficult to meet because interfaces were application-specific. The remaining business requirements could not be met effectively for this same reason.
The technical requirement of having a solution work correctly and the operational requirement of meeting the specific needs of an organization were difficult to satisfy. Because the interfaces required extensive programming, it was difficult to avoid bugs. For the same reason, operational flexibility was difficult and costly to achieve.
The technical requirement and operational requirement were at odds with the requirement of cost effectiveness. Since each coupling had to be programmed separately, the cost was proportional to the number of couplings.

Second Generation: Fire-and-Forget

The biggest drawback of first-generation solutions was that they didn't perform well over large, geographically-distributed systems. Because globalization was (and is) a non-negotiable requirement in business integration, a new solution was needed.

The second-generation solutions addressed the globalization issue by employing a fire-and-forget strategy. An example of this is the Microsoft Message Queue (MSMQ) technology. The idea was that instead of tight coupling, messages were used for communication. The messages were placed in the queue by using a message broker, and they could be processed at a later time, thus enabling asynchronous communication. With this approach, there still was a need for some mechanism to do the actual processing. Therefore, the solutions such as DCOM weren't replaced by this approach, but rather, they were augmented by it.

Using the human languages analogy again, with this type of solution you still need interpreters for every language pair. The difference is that if the interpreter is not available at a particular moment, you can put the text you want translated on his desk to be translated as soon as he becomes available. Since you do not have to wait for the interpreter, you can go and do other things and the interpreter will let you know when he's completed his task. Your translation will be done when the interpreter becomes available. In this way, the waiting is reduced and the system availability is significantly improved. But because the interpreter might have a large stack of papers to translate, he needs to manage those papers in a predetermined way. For integration purposes, a good mechanism for managing the items to be translated is a queue. So, the central idea for the second-generation integration systems was a queuing mechanism.

Figure 1.2 The second generation of integration

Although the second-generation integration solutions represented significant progress on the road toward system integration, they were far from ideal. Most used proprietary technology and were therefore expensive to buy and maintain. Another problem is that while these systems worked well within an organization, they didn't scale well outside an organization's boundaries.

What about risk-management requirements for these second-generation solutions? Again, there was the same problem as encountered with the first-generation solutions: technical and operational criteria were outweighed by the financial costs of the solutions. In addition, by the time these solutions became available, the need for cross-business communication became even more pressing.