1. What is the Windows Presentation Foundation?

The Windows Presentation Foundation is the

unified presentation subsystem for Windows. It consists of a display engine and a managed-code
framework. The Windows Presentation Foundation unifies how Windows creates, displays, and
manipulates documents, media, and user interface, which enables developers and designers to
create visually-stunning, differentiated user experiences that improve customer connection. When it
ships, scheduled for 2006, the Windows Presentation Foundation will be available on Windows XP,
Windows Server 2003 and all future releases of the Windows operating system. When delivered, the
Windows Presentation Foundation will become Microsoft’s strategic user interface technology.

2. What is the Windows Communication Foundation?

The Windows Communication Foundation is a set of technologies for building and running connected
systems.

The Windows Communication Foundation is a new breed of communications infrastructure built

around the Web services architecture. Advanced Web services support in the Windows
Communication Foundation provides secure, reliable, and transacted messaging along with
interoperability. The Windows Communication Foundation’s service-oriented programming model is
built on the .NET Framework and simplifies development of connected systems. The Windows
Communication Foundation unifies a broad array of distributed systems capabilities in an extensible
architecture, spanning transports, security systems, messaging patterns, encodings, network
topologies and hosting models. The Windows Communication Foundation will be an integral capability
of Windows Vista and will also be supported on Windows XP and Windows Server 2003.

Microsoft has also done significant work to integrate the Windows Communication Foundation with
existing Microsoft technologies for building distributed systems including COM+, MSMQ, and
ASP.NET Web services. Applications built with those existing technologies can now be exposed as
services without modification to the application. This infrastructure-level solution greatly assists
developers in exposing existing applications as services. The Windows Communication Foundation
also provides simple and mechanical mechanisms to migrate applications that use .NET remoting,
ASP.NET Web services, and .NET Enterprise Services to natively use the Windows Communication
Foundation programming model.

3. Is C# used for any core features of Windows Vista?

Yes, for example, much of the Windows Presentation Foundation is written using C#

4. Why do we need XAML as a new way to create applications in .NET Framework 3.0
(formerly WinFX)?
The new application model in Windows Vista separates out declarative code (XAML) from procedural
code (C#, VB.NET, J#, etc.). One major reason for using XAML is to bridge the gap between
developing an application for Microsoft Windows and developing an application for the Web.

XAML does not give you new functionality; it is just a declarative way to instantiate and initialize
Microsoft .NET objects. XAML does, however, provide you with a way to solve problems such as:
When you write procedural code (C#, etc.) to create a number of controls, and compare that to the
equivalent XAML, the XAML is more compact, less redundant, and less error-prone. Writing a
designer for XAML will be a lot easier than writing a forms designer for C# or VB.NET, since the
designer won’t have to do all that code parsing to figure out where to insert or change the setting of a
property.
In the real world, many customers find requests coming in at the very last minute asking for changes
to the user interface—a button needs to be moved or removed or the company logo needs to appear
on every window. It is especially at the end of the development process, when you think your code is
“frozen” and tested, that you’d rather not have to dive into the source code and start changing things.
Who knows what subtle interaction you might break? With XAML, most—if not all—of the presentation
layer is in its own file, thus providing a high degree of certainty that making a user interface change in
the XAML will not break business logic code.

XAML enables professional graphic designers or user interface specialists to add beauty, style and
grace to an application without modifying source files directly. Partitioning the user interface and the
logic that drives it means each of us can get our job done without getting in each other’s way or
having to understand the myriad details of one another’s tools.

XAML is considerably smaller than the equivalent C# code. Since there is less code, there are fewer
opportunities for errors

5. Is XAML only used for quick UI prototyping?

XAML will be used for production work, not just for prototyping. Specifically, localizing your application
or ensuring that it is accessible—common for most applications today—will be a lot more work if you
build your own user interface from code instead of using XAML

6. Will XAML replace other programming languages like C# and VB?

No. XAML complements procedural languages, much the same way HTML complements
ECMAScript. You can very quickly declare how you want your user interface to look with XAML, then
use a language like C# to define the business logic behind that user interface

7. Can XAML be used to develop both Web and client-server applications?

XAML is used as part of Windows Presentation Foundation to write smart client applications that take
advantage of the power of the PC and benefit from all of the power of the CLR. For Windows
Presentation Foundation applications, the logic runs on the client, unlike ASP.NET, which processes
on the server. ASP.NET continues to be the answer to producing powerful Web applications that take
advantage of the benefits of the CLR on the server

8. Q: What is NET Framework 3.0 ?

A: NET Framework 3.0 is the managed-code programming model for Windows, starting with Windows
Vista. NET Framework 3.0 is a superset of the .NET Framework, designed to expose the new
functionality in Windows Vista to the developer through managed classes. If you know how to write
managed code on the .NET Framework today, NET Framework 3.0 will be familiar to you. Put another
way, at PDC 2000, Microsoft debuted the .NET Framework, which introduced a new managed
programming model on top of our existing Windows operating systems. With Windows Vista and NET
Framework 3.0, we’re keeping that managed programming model while building new core parts of the
operating system, such as moving the Windows Presentation Foundation subsystem next to GDI and
User.

9. Q: What is the difference between Windows Vista and .NET Framework 3.0 ?
A: The .NET Framework 3.0 is a managed-code programming model, including APIs for the Windows
Presentation Foundation and the Windows Communication Foundation.

10. Q: Where is the new functionality in the .NET Framework 3.0 (such as WCF, WF, WPF, and
CardSpace) installed to? Is that different from where the .NET Framework 2.0 is installed to?
A: Components shared with the .NET Framework 2.0 are installed at %windir
%\Microsoft.NET\Framework\V2.0.50727. Components that are new to the .NET Framework 3.0 are
installed to %windir%\Microsoft.NET\Framework\V3.0. Check out the .NET 3.0 Deployment
whitepaper for more information on installation and deployment.

11. Q: How large is the .NET Framework 3.0? Does this change make the release larger?
A: There’s no change to the size of the .NET Framework 3.0 as a result of the name change from
WinFX. It is about 49Mb, and that includes the .NET Framework 2.0, which is about 22Mb.

12. Q: How does servicing work for the .NET Framework 3.0? If I install the .NET Framework
3.0, can I get service updates for the .NET Framework 2.0?
Servicing will be available for the .NET Framework 2.0 components as long both it and the operating
system it is installed on are still in service. Any service updates for the .NET Framework 2.0 will work
for the 2.0 components installed as a part of the .NET Framework 3.0 as well.

13. Q: What operating systems will the .NET Framework 3.0 be available for?
A: The .NET Framework 3.0 will be available for and supported on Windows Vista, Windows Server
2003 (SP1), Windows Server 2003 SP2, and Windows XP (SP2).

14. Q: When will the .NET Framework 3.0 be released? A: The .NET Framework 3.0 is included as
part of Windows Vista, and customers who get Windows Vista will receive the .NET Framework 3.0.
The first release of Windows Vista to business customers is currently planned for November 2006,
although the final date will depend on customer feedback.
At the same time, we will make the .NET Framework 3.0 broadly available for download to all
customers using Windows XP and Windows Server 2003.

15. Q: How does the .NET Framework 3.0 relate to Windows Vista? A: The .NET Framework 3.0
is a core component of the Windows Vista operating system, and is installed by default on Windows
Vista. It will also be available for Windows XP and Windows Server 2003.

16. Q: Are there any parts of the .NET Framework 3.0 that only work on Windows Vista? A:
Though there are some optimizations in the .NET Framework 3.0 that take advantage of new
functionality in Windows Vista, we’ve striven to provide a consistent experience for the .NET
Framework 3.0 across Windows Vista, Windows Server 2003, and Windows XP.

17. Q: Why is the .NET Framework 3.0 a major version number of the .NET Framework if it
uses the .NET Framework 2.0 runtime and compiler?
A: The new technologies delivered in the .NET Framework 3.0, including WCF, WF, WPF, and
CardSpace, offer tremendous functionality and innovation, and we wanted to signal that with a major
release number.

18. Q: How does “Side by Side” work for the .NET Framework 3.0?
A: Since the .NET Framework 3.0 includes only new components that are added to the .NET
Framework 2.0 and there is no overlap between the assemblies of the .NET Framework 2.0 and
the .NET Framework 3.0, there’s no real “Side by Side” scenario. You can run applications based on
the .NET Framework 2.0 and applications based on the .NET Framework 3.0 on the same machine.

19. Q: I’m running an application built on WinFX today. Do I need to do anything different to
make it run on the .NET Framework 3.0?
A: No, applications running on WinFX will now run on the .NET Framework 3.0 without any changes.
Of course, since the .NET Framework 3.0 is still under development, there may be changes to the
framework in the future.
20. Q: Can I remove particular .NET Framework 3.0 components?
A: No, the .NET Framework 3.0 components (WPF, WCF, WF, and CardSpace) are part of a single
package, and are installed together.

21. Q: Will C# 3.0, VB.NET 9.0, Atlas, or Linq be included in the .NET Framework 3.0?
A: No, these features are planned for future releases of the .NET Framework. The .NET Framework
3.0 includes only the technology formerly described as WinFX.

22. Q: Will there be a .NET Compact Framework 3.0 release with release of .NET Framework
3.0?
A: No. We are currently working on developing a version of the .NET Framework 3.0 functionality that
will be supported on the Compact Framework, but shipping plans and included functionality have not
been announced.

23. Q: What is the version number for the next version of the .NET Framework, codenamed
“Orcas”?
A: We’re still planning the “Orcas” release, and so this number is not yet defined.

24. Q: What happens when I install the .NET Framework 3.0? How can I upgrade if I already
have the .NET Framework 2.0 installed?
A: When you install the .NET Framework 3.0, the installer will check to see whether you already have
the .NET Framework 2.0 (released version) installed. If not, the .NET Framework 3.0 installer will
install the .NET Framework 2.0 for you, and then install the new .NET Framework 3.0 components. If
you do have the .NET Framework 2.0 installed, the .NET Framework 3.0 installer will only install the
new components of the .NET Framework 3.0.

25. Q: My organization went through the approval process of supporting the .NET Framework
2.0 in production. Do we need to go through the same process all over again for the .NET
Framework 3.0? Do I need to do any application compatibility testing for my .NET Framework
2.0 applications?
A: Because the .NET Framework 3.0 only adds new components to the .NET Framework 2.0 without
changing any of the components released in the .NET Framework 2.0, the applications you’ve built on
the .NET Framework 2.0 will not be affected. You don’t need to do any additional testing for your .NET
Framework 2.0 applications when you install the .NET Framework 3.0.

26. Q: Will the name change be reflected in any of the existing .NET Framework 2.0 APIs,
assemblies, or namespaces?
A: There will be no changes to any of the existing .NET Framework 2.0 APIs, assemblies, or
namespaces. The applications that you’ve built on .NET Framework 2.0 will continue to run on the
.NET Framework 3.0 just as they have before.

27. Q: Which version of the Common Language Runtime (CLR) does the .NET Framework 3.0
use?
The .NET Framework 3.0 uses the 2.0 version of the CLR. With this release, the overall developer
platform version has been decoupled from the core CLR engine version. We expect the lower level
components of the .NET Framework such as the engine to change less than higher level APIs, and
this decoupling helps retain customers’ investments in the technology.

28. Q: What is the .NET Framework 3.0 (formerly WinFX)?

A: The .NET Framework 3.0 is Microsoft’s managed code programming model. It is a superset of
the .NET Framework 2.0, combining .NET Framework 2.0 components with new technologies for
building applications that have visually stunning user experiences, seamless and secure
communication, and the ability to model a range of business processes. In addition to the .NET
Framework 2.0, it includes Windows Presentation Foundation (WPF), Windows Workflow Foundation
(WF), Windows Communication Foundation (WCF), and Windows CardSpace.

29. Q: What happens to the WinFX technologies?

A: The WinFX technologies will now be released under the name .NET Framework 3.0. There are no
changes to the WinFX technologies or ship schedule — the same technologies you’re familiar with
now simply have a new name.

30. Q: How does the .NET Framework 3.0 relate to the .NET Framework 2.0?
A: The .NET Framework 3.0 is an additive release to the .NET Framework 2.0. The .NET Framework
3.0 adds four new technologies to the .NET Framework 2.0: Windows Presentation Foundation
(WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and
Windows CardSpace. There are no changes to the version of the .NET Framework 2.0 components
included in the .NET Framework 3.0. This means that the millions of developers who use .NET today
can use the skills they already have to start building .NET Framework 3.0 applications. It also means
that applications that run on the .NET Framework 2.0 today will continue to run on the .NET
Framework 3.0.

31. Is XAML only used for quick UI prototyping?

XAML will be used for production work, not just for prototyping. Specifically, localizing your application
or ensuring that it is accessible—common for most applications today—will be a lot more work if you
build your own user interface from code instead of using XAML

32. Will XAML replace other programming languages like C# and VB?
No. XAML complements procedural languages, much the same way HTML complements
ECMAScript. You can very quickly declare how you want your user interface to look with XAML, then
use a language like C# to define the business logic behind that user interface

33. Can XAML be used to develop both Web and client-server applications?
XAML is used as part of Windows Presentation Foundation to write smart client applications that take
advantage of the power of the PC and benefit from all of the power of the CLR. For Windows
Presentation Foundation applications, the logic runs on the client, unlike ASP.NET, which processes
on the server. ASP.NET continues to be the answer to producing powerful Web applications that take
advantage of the benefits of the CLR on the server

34. Why do we need XAML as a new way to create applications in .NET Framework 3.0
(formerly WinFX)?
The new application model in Windows Vista separates out declarative code (XAML) from procedural
code (C#, VB.NET, J#, etc.). One major reason for using XAML is to bridge the gap between
developing an application for Microsoft Windows and developing an application for the Web.XAML
does not give you new functionality; it is just a declarative way to instantiate and initialize Microsoft
.NET objects. XAML does, however, provide you with a way to solve problems such as:

When you write procedural code (C#, etc.) to create a number of controls, and compare that to the
equivalent XAML, the XAML is more compact, less redundant, and less error-prone. Writing a
designer for XAML will be a lot easier than writing a forms designer for C# or VB.NET, since the
designer won’t have to do all that code parsing to figure out where to insert or change the setting of a
property.
In the real world, many customers find requests coming in at the very last minute asking for changes
to the user interface—a button needs to be moved or removed or the company logo needs to appear
on every window. It is especially at the end of the development process, when you think your code is
“frozen” and tested, that you’d rather not have to dive into the source code and start changing things.
Who knows what subtle interaction you might break? With XAML, most—if not all—of the presentation
layer is in its own file, thus providing a high degree of certainty that making a user interface change in
the XAML will not break business logic code.

XAML enables professional graphic designers or user interface specialists to add beauty, style and
grace to an application without modifying source files directly. Partitioning the user interface and the
logic that drives it means each of us can get our job done without getting in each other’s way or
having to understand the myriad details of one another’s tools.

XAML is considerably smaller than the equivalent C# code. Since there is less code, there are fewer
opportunities for errors

35. What is XAML?

“XAML, Extensible Application Markup Language, is Microsoft’s XML-based language for creating a
rich graphical user interface….XAML was introduced in 2003 as the language behind Windows
Presentation Foundation, then known as Avalon.”

36. Why do we need XAML?

Well, OK, in the real world, there’s been a move towards declarative programming for a while. XAML
is in some ways a logical successor to SGML-based markup languages like HTML and XML. Although
of course XAML is an XML dialect it provides a way to bind presentational data (the declarative list of
UI elements) with some or all of the code used with them. Now why, you might ask, would Microsoft
be so bothered about that? Simply put, Microsoft needs to find new ways to exploit the processing
power of the client as well as the server, if it is to continue selling operating systems for the next few
decades. If true thin-client computing ever really got started, it would eviscerate the OS market. That’s
what Google is aiming for, and it’s exactly the thing that Microsoft fears.XAML allows you to export
processing to the client machine in a way that mere script doesn’t. In effect, you can stream the
interface of an application, plus a portion (or even all) of its logic, over the wire using a protocol that’s
open on most firewalls. You can stream XAML into the browser and get something roughly equivalent
to ActiveX controls or Java applets (which exports .NET to the browser as Silverlight has done,
something Microsoft has been planning for a while). Silverlight is the first fruit of this particular
plan.However, don’t expect XAML-over-HTTP to stay within the browser for long. It’s a perfect way to
provide desktop apps without installers, software-as-a-service, all the stuff Microsoft was supposed to
be planning years back when people were still talking about Windows.NET - you didn’t think they just
gave up on all that stuff, did you?Add to this the bare-metal hypervisor stuff they are developing -
‘Viridian’ for Windows Server 2008 will be a hobbled implementation of this, but there’s more coming,
and it will likely be the core architecture of whatever ‘Vienna’ turns out to be - and you can see a
model developing of (supposedly) safe, sandboxed, virtualised applications streamed from the net
over fast connections, always up to date, running partially on the client and partially on the server,
potentially replacing today’s stateless browser-based model of internet application.I doubt the reality
will live up to the dream - it never does with Microsoft, any more than it does with anyone else - but
that’s the reason they want you to buy into XAML in a nutshell.

37. What is XAML?

Transaction Authority Markup Language (XAML) is a vendor-neutral standard that enables the
coordination and processing of online transactions in the rapidly emerging world of XML web services
- the revolutionary new model of Internet-based computing that is now being adopted by all major
systems and software vendors. XAML is intended to be a completely open standard for web-based
business transactions.The standard defines a set of XML message formats and interaction models
that web services can use in order to provide business-level transactions that span multiple parties
across the Internet.

38. Why is XAML important for the delivery of e-commerce solutions?

As plug-and-play e-commerce emerges, businesses are mixing and matching web services from
multiple partners to create sophisticated business web services. Because these “business webs” are
comprised of aggregated calls to loosely coupled web services distributed across the web, and
provided by multiple businesses, coordination among these web services is imperative, in order to
carry out business-level transactions. There needs to be the notion of a transaction at the web service
level, as well as a means by which software systems can coordinate the processing of calls to multiple
web services to provide higher-level business transactions.

XAML will provide the standard mechanism to enable XML web services to participate in business
transactions spanning multiple parties across the Web. Web services provide unprecedented
business interoperability by enabling businesses to share processes and competencies on the web,
creating a new era of business connectivity and dynamic, “plug-and-play” e-commerce.

39. What kind of applications will XAML enable?

As plug-and-play e-commerce emerges, businesses are mixing and matching web services from
multiple partners to create sophisticated e-business applications. Because these “business webs”
consist of loosely coupled web services distributed across the web from multiple businesses,
coordination among these web services is imperative, in order to carry out business-level
transactions. There needs to be the notion of a transaction at the web service level, as well as a
means by which software systems can coordinate the processing of calls to multiple web services to
provide higher-level business transactions.

40. Who is supporting XAML?

Bowstreet, Hewlett-Packard, IBM, Oracle and Sun are leading the XAML initiative to ensure
distributed e-business transactions across the Internet. However, XAML is not owned by any one
vendor. Instead, the standards proposal will be submitted to an appropriate open standards body to
ensure that it remains an open industry standard in which any company and organization can
participate.

41. How does XAML relate to other Web Service standards?

In order to understand how XAML relates to many of the existing standards, it is first necessary to
understand what function each of these standards performs.When a web service is built, described,
discovered and used, there are many elements that will be required. The combination of these many
different elements is called a web services architecture. Some categories of these elements are:
registries, business process modeling, negotiation, service description and web service transport
protocols.

In order to use a web service, the existence of the service must be discovered. This discovery usually
takes place in a “phone book” of web services known as a registry. Registries, such as UDDI and the
ebXML registry/repository, contain human readable information that can be browsed and searched to
find companies and their services.

Once a desired service is located, the terms of use can be reviewed and/or negotiated. The e-speak
framework provides an elaborate negotiation mechanism. ebXML addresses the same issue through
TPAML (Trading Partner Agreement Markup Language.)
Now that you know which service you need, you still have to know some additional things before you
can use the web service; where is it located, what type of input it expects, what type of output it
produces, which web service protocols it uses, etc. Service description languages, such as WSDL,
provide a standard mechanism to outline all these details about a web service. Typically, for publicly
available web services, their service descriptions are also made publicly available. The URI of the
service description can be registered with a web service in a registry.

Once you know those details, you can start formulating a message to send to the service. However,
some web services will require special packaging wrapped around the message, letting the web
service know what to do with the message.

In this situation, an underlying web service transport protocol may need to be used, which can
provide: an envelope which defines what is in a message and what program should deal with it2.
specific information about how to exchange instances of application-defined data-types in a serialized
format (You can think of this as how the programs agree on the format of a text-based XML file to
send across the internet which contains information about a relational database or other complicated
data structure within an application)3. a definition of a convention that can be used to represent
remote procedure calls and responses.

XML-based web service transport protocols include: SOAP, XP (W3C XML Protocol) and ebXML
Transport. Most of these web service transport protocols make use of existing protocols, such as:
HTTP, SMTP, TCP, etc., to carry web service requests and responses across the internet.Another
layer in the web services architecture is business process modeling. These languages define the
business level descriptions of what needs to be accomplished. For example, they can describe a
business scenario such as, “if a purchase order is received by my purchasing web service, the steps
that need to be completed are: check inventory; if the inventory is available, ship product; if product
ships, let accounting know, etc.” Business process modeling languages determine what needs to be
completed and the necessary order of completion. However, they do not control nor monitor the
underlying transactions themselves, where XAML is used to initiate, monitor, commit, cancel, retry, or
initiate a compensating transaction.Consider this web services architecture example: A distributor of
groceries needs to process an order from ACME grocery store. Included in the order is an order for
100lbs of fresh tomatoes. The grocery distributor needs to process this order. In order to fulfill this
order the web services architecture will be used in a variety of ways.

The first requirement (even before the distributor gets the order) is to discover that Johnny’s Tomato
Farm and Jimmy’s Refrigerated Transport provide the necessary business services. Both services are
discovered via a registry; in this case, the distributor searched several different registries.

The second action is to make sure the distributor’s business web understands how to talk with each of
these web services. This is done by downloading a service description for each of the two services.
The registry entry indicated that Jimmy’s Refrigerated Transport is described as an e-speak service;
whereas, Johnny’s Tomato Farm services are based solely on SOAP. An XML description is retrieved
for the e-speak service and a WSDL document is retrieved for the SOAP service. Links to the service
description documents were found in the registry entries.

An additional action must also happen before the order is placed. The business process model of a
purchase order must be executed. 1)check to make sure that the person ordering is authorized to
order; 2)check to make sure the ordering company has paid their last invoice; and 3)proceed to order
the merchandise by ensuring that both services get managed using XAML. This entire business
process is defined by an ebXML business process model. Some additional models may need to be
set up…. If the item is perishable, then verify the transport availability, etc.
Now, the grocery distributor is ready for action and can accept a tomato order from ACME grocery
store.

The order from ACME grocery store is taken via the distributor’s business web, and according to the
business process model, the person is authorized and the finance department gives the approval. The
transaction is begun on a business level. Because Tomatoes are marked as perishable, the
“perishable food” model is initiated.

This model determines the business logic which states that transport must be arranged before
tomatoes can be officially ordered. This logic is then used by the software that coordinates the calling
of the relevant web services. The calling system prepares a message directed to a web service at
Johnny’s Tomato Farm using SOAP, along with XAML to specify initiation of the transaction. In like
manner, the system requests a web service at Jimmy’s Refrigerated Transport to supply the truck and
driver, again using XAML to stage the request. Once both web services have responded confirming
availability, the calling system interacts with the web services using XAML to facilitate the completion
of the business process.

42. How does XAML relate to registries (UDDI)?

UDDI defines a registry for companies and their services. In a typical scenario using UDDI, a
user/program would browse through categories (like in a yellow pages) for a particular service. Once
the desired XML service is found, the ’service description’ for that service can be used to retrieve the
details of calling that service (see service description languages section.) The ‘service description’
(WSDL, etc), defines the semantics of calling a specific service.
As with any other type of service, XAML services will be able to be registered and located within UDDI
registries. UDDI can register XAML services.

43. How does XAML relate to service description languages (WSDL, XMI)?
Services description languages define the details that are needed to use a web service. Typically that
includes: schema for the input, schema for the output, URI of the service, type of transport used
(SOAP, XP, HTTP GET, …) The XAML group will consider providing binding information to service
description languages.

44. How does XAML relate to business process modeling languages (ebXML business
process, BPML)?
BPML covers dimensions of business process modeling that are specific to processes internal to the
enterprise, including business rules, security roles, distributed transactions, and exception handling.
XAML is targeted at coordinating business transactions that span web services crossing corporate
boundaries.

45. How does XAML relate to XML-based web service transport protocols (XP, SOAP, ebXML
Transport)?
XAML is designed for the coordination of transactional web services, not XML transportation and
packaging issues. XAML will work with standard XML-based service transport protocols, including
W3C XML Protocol (XP), SOAP and ebXML transport protocol.

46. How does XAML relate to ebXML?

ebXML is an OASIS/UN initiative to define all the layers in the web services stack. That includes
categories such as registries, business process modeling, service descriptions, and
transport/packaging/messaging. Please refer to the above explanation for details on how XAML
relates to each of these categories.
47. How does XAML relate to e-speak?
E-speak is an open software platform designed for supporting the description, registration, and
discovery of e-services, the ability to compose multiple e-services into higher-level e-services, the
ability to negotiate among e-services, and the ability to manage e-service interactions. XAML will
enhance the e-speak platform for the coordination and processing of online business transactions
involving e-services. XAML provides e-speak with a standard set of XML message formats and
interaction models for e-services to use to provide business level transactions that span across
companies over the Internet.

48. How does XAML relate to BizTalk/.NET?

BizTalk/.Net is a Microsoft initiative to define all the layers in the web services stack. That includes
four categories, registries(UDDI), business modeling languages (X-Lang), service descriptions
(WSDL), and transport/packaging/messaging(SOAP). Please refer to the above explanation for details
on how XAML relates to each of these categories.

49. What standards body will XAML be submitted to?

At this time, the XAML group has not determined which standards body is the most appropriate for
XAML. However, as the specification evolves, the group will vote on an appropriate organization and
submit a draft of the specification.

50. How does XAML support/extend existing transaction monitors?

XAML will enable web services to expose transactional semantics of the resources providing the
services. Given that TP monitors commonly provide some of the management and coordination
functions of these resources ‘behind the firewall” today, one of the goals of XAML is to enable TP
monitors to participate and support the transactional semantics offered by web services. This includes
passing of transaction ID’s through web service messages, and supporting the XAML web service
operations of commit and cancel. At the level above individual web services, there is a new layer of
software providing business-level transactions. This software makes calls to multiple web services,
often spanning business boundaries. Given that XAML enables individual web services to support
transactional semantics, there is also an opportunity for XAML to specify standard means for
coordinating business-level transactions across collections of web services. To this end, one of the
goals of XAML is to define message interfaces and interaction models that help software systems
providing the business-level transactions to coordinate the interactions among web services. There is
an opportunity to define XML interfaces and interaction models for a new breed of web services that
would help software systems at the business transaction level. These services would provide
brokering capabilities for managing the interactions among web services, for both web services
supporting XAML, as well as web services that do not support XAML. This new breed of web services
requires XML interfaces and interaction models that defines how software systems at the business
transaction level would interact, to request assistance in shepharding a set of web services towards
completion.

51. What is the relationship between XAML and other transaction protocols?
Classical online transaction management (OLTP) is the process of making simultaneous changes in
several places “atomically” - that is, all the changes related to a transaction are made or none of the
changes are made.
For example, within a single database connection, the DBMS provides some means of demarcating
the beginning and end of a transaction. This demarcation ensures that changes to the database are
made atomically. Sometimes, changes must be made atomically across multiple databases. For
example, an insurance company might have to change both its claims information and its audit
information at the same time, even though the audit information is in a separate database from the
claims information. This multiple-database change would ensure that, during a later audit, the
company would know which agent took the first report of the loss. In this case, the existing XA
(Transaction Authority) protocol is useful. XA provides a standard mechanism for coordinating
changes to multiple databases (called resource managers or RMs) as an atomic unit of work.
Basically, the XA protocol asks each RM to vote on whether a commit will be successful. Once an RM
has voted “yes,” it must be able to commit the open unit of work without failure. The commit occurs
only if all RMs vote “yes.” This process of obtaining a vote, and then performing a commit, is called a
“two-phase commit.”

Resource managers are most frequently databases, but they can also be message-oriented
middleware. XA allows completely heterogeneous collections of RMs within a single transaction; for
example a transaction can commit across DB/2 and Oracle at the same time. All major database
vendors support XA.

52. What is the relationship between XAML and JTS/JTA?

J2EE includes support for distributed transactions through two specifications, Java Transaction API
(JTA) and Java Transaction Service (JTS). JTA is a high level, implementation independent, protocol
independent API that allows applications to access transactions. JTS specifies the implementation of
a Transaction Manager which supports JTA and implements the Java mapping of the OMG Object
Transaction Service (OTS) 1.1 specification using the IIOP protocol. The JTA API allows you to
demarcate transactions in a manner that is independent of the transaction manager service or JTS.

While JTA provides an API for demarcating transactions in Java-based application logic, XAML
provides an agreed upon protocol or a coordinated process of interaction among transactionally-
aware web services over a defined transport. Given this, a web service internally implementing JTA
could expose these transactional capabilities using XAML.

53. What is XAML?

(Extensible Application Markup Language; pronounced “zammel”)
XAML is a declarative XML-based language that defines objects and their properties in XML. XAML
syntax focuses upon defining the UI (user interface) for the Windows Presentation Foundation (WPF)
and is therefore separate from the application code behind it.
Although XAML is presently for use on the Windows platform, the WPF/E (Windows Presentation
Foundation/Everywhere) initiative will eventually bring XAML to other platforms and devices.
XAML syntax describes objects, properties and their relationships to one another. Generic XAML
syntax defines the relationship between objects and children. Properties can be set as attributes or by
using ‘period notation’ to specify the object as a property of its parent.

54. Why Use XAML?

XAML allows the programmer to separate the user interface (UI) definition from the underlying
business logic. XAML, since it is parsed, offers the possibility that a single UI definition can be used
on different platforms XAML allows the user to edit the presentation layer (not necessarily directly, but
with a simple tool) without requiring the usual development tools or programming knowledge

55. How Is XAML Used?

XAML is used for both web-based and client-based applications. Within those two segments, there
are three camps regarding the usage of XAML:
Declaratively programming 2D and 3D vector graphics (VG)
Declaratively programming traditional (meaning no VG) UI’s and their controls (or widgets)
As a general declarative programming language for UI and non-UI constructs

56. What is .NET 3.0 ?

57. What is WCF?

58. What are the important principles of SOA (Service oriented Architecture)?

59. What are end points, contract, address and bindings?

60. What are bindings?

61. Which specifications does WCF follow?

62. What are the main components of WCF?

63. Can you explain how End points, Contract, Address and Bindings are done in WCF?

64. What is a service class?

65. What is a service contract, operation contract and Data Contract?

66. What are the various ways of hosting a WCF service?

67. What are the major differences between services and Web services?

68. What is the difference WCF and Web services?

69. What are different bindings supported by WCF?

70. Which are the various programming approaches for WCF?

71. What is one way operation?

72. Can you explain server controls in Atlas?

73. Can you explain ScriptManager control?

74. What is the importance of UpdatePanel Control?

75. Can you explain update progress control?

76. Can you explain control extenders?

77. How can we data binding in Atlas?

78. Can you explain AtlasUIGlitz library?

79. I want to create a project like Google maps how can we do that with Atlas?

80. How can we integrate Atlas with Web services?

81. How can implement drag and drop using Atlas?

82. How do we do authentications using Atlas?

83. How can we access profiles using Atlas?

84. How can we access dataset in Atlas?

85. Can you explain duplex contracts in WCF?

86. How can we host a service on two different protocols on a single server?

87. How can we use MSMQ bindings in WCF?

88. Can you explain transactions in WCF?

89. What different transaction isolation levels provided in WCF?

90. Can we do transactions using MSMQ?

91. Can we have two way communications in MSMQ?

92. What are Volatile queues?

93. What are Dead letter queues?

94. What is a poison message?

95. WPF Interview questions What is WPF?

96. What is XAML?

97. What are different types of Workflow in Windows Workflow foundation?

98. When should we use a sequential workflow and when should we use state machiHow

99. Do we create workflows using designer?

100. How do we specify conditions in Work flow?

101. How do you handle exceptions in workflow?

102. What is the use of XOML files?

103. Twist: - How can we serialize workflows?

104. How can we pass parameters to workflow?

105. AJAX Interview questions

106. What problem does Ajax solve?

107. What is Ajax?

108. What is the basic fundamental behind Ajax?

109. What is JSON?

110. How do we use XMLHttpRequest object in JavaScript?

111. How do we do asynchronous processing using Ajax?

112. What are the various states in XMLHttpRequest and how do we check the same?
113. How can we get response text?

114. How can we create XMLHttpRequest component?

115. How can we create a class in JavaScript using Atlas?

116. How do we do inheritance using Atlas?

117. How do we define interfaces using Atlas?

118. How do we reference HTML controls using Atlas?

119. Can you explain server controls in Atlas?

120. Can you explain ScriptManager control?

121. What is the importance of UpdatePanel Control?

122. Can you explain update progress control?

123. Can you explain control extenders?

124. How can we data binding in Atlas?

125. Can you explain AtlasUIGlitz library?

126. What are dependency properties?

127. Are XAML file compiled or built on runtime?

128. Can you explain how we can separate code and XAML?

129. How can we access XAML objects in behind code?

130. What are the kind of documents are supported in WPF?

131. Windows workflow foundation(Vista series)

132. What is Windows Workflow Foundation?

133. What is a Workflow?.

134. I want to create a project like Google maps how can we do that with Atlas?

135. How can we integrate Atlas with Web services?

136. How can implement drag and drop using Atlas?

137. How do we do authentications using Atlas?

138. How can we access profiles using Atlas?

139. How can we access dataset in Atlas?

140. What is Windows Communication Foundation?

141. What is Windows Presentation Foundation?

142. What is Windows Workflow Foundation?

143. What is Windows CardSpace?

144. Are there advantages to building workflows using only XAML? Are there
disadvantages?

145. What are the pros and cons of using an ExternalDataExchange service versus going
directly to the WorkflowQueuingService?

146. When are attached dependency properties useful in WF programming?

147. What behavior does the default scheduling service provide?

148. How can my code participate in a database transaction with a workflow instance?

149. Why would I use a tracking service?

150. Describe a scenario where the WF runtime will cancel an executing activity.

151. Describe a scenario where I’d need to spawn a new ActivityExecutionContext.

152. Tell me why I’d use a compensation handler.

153. Tell me about the following activities: Replicator, Parallel, and Policy.

154. Are there advantages to building workflows using only XAML?

155. Are there disadvantages in building workflows using XAML?