Cache Distribuído

Requisitos para certificação de uma aplicação Windows 8: Como fazer para sua aplicação ser publicada na Windows Store do Windows 8

Garry Trinder — Fri, 18 May 2012 09:43:42 GMT

Oi pessoal. Segue uma referência para certificar sua aplicação na Windows Store do Windows 8. Todos os passos devem ser seguidos rigorosamente. Abs, @daibert Important This is a preview version of the Windows 8 app certification requirements and is provided is for your information only. See Certification requirements for the current version of this document. In this document, we describe the criteria an app must meet to be eligible for listing in the Windows Store.

Welcome

Thank you for your interest in developing apps for Windows. We’re committed to a relationship with you that supports your ambitions and encourages a diverse catalog of high-quality, engaging apps for Windows customers worldwide. We crafted these certification requirements with those goals in mind and they should help you make choices that enhance your app’s appeal and help speed its listing in the Windows Store. We review every app before we list it in the Store. If our certification requirements change, we’ll identify the updates to ease your consideration. If you have feedback on the policies, please let us know by commenting in our forum. We will consider every comment. Your apps are crucial to the experience of hundreds of millions of customers. We can’t wait to see what you create and are thrilled to help deliver your apps to the world.

1. Metro style apps provide value to the customer

1.1 Your app must offer customers unique, creative value or utility

1.2 Your app must be fully functional when the customer gets it from the Windows Store

The Windows Store offers only fully functional apps to provide customers with the best experience. Anything that might cause our testers to think that your app is not completely finished will cause your app to fail certification. You can help us by testing your app thoroughly before you submit it, and by providing us the information we need to test your app thoroughly. For example, if your app requires login credentials, provide us with a demo account. If your app requires access to a server, tell us what we need to do verify that it's working correctly.

1.3 Your app’s trial functionality must reasonably resemble its full functionality

A trial can limit access to some of the app’s features, or limit the period of time that the app functions.

1.4 Each app must display only one tile after it is installed

The image on an app’s tile must be reasonably related to the content of the app.

2. Metro style apps can display ads but are more than just ads or websites

2.1 Your app must not display only ads

If your app includes or displays ads, it must provide additional functionality beyond the ads.

2.2 Ads in your apps must comply with our content policies

Our content policies are described in Section 5. Metro style apps are appropriate for a global audience.

2.3 Your app must not use its tiles, notifications, app bar, or the swipe-from-edge interactions to display ads

2.4 The primary experiences your app provides must take place within the app

2.5 Ads must not execute program code that didn't come from the ad provider

3. Metro style apps behave predictably

3.1 Your app must adhere to the Metro style app model

You must use only the Metro style APIs to implement the features of your app. We describe these APIs in the Metro style apps API reference. Your app must not link to, depend on, or otherwise make use of APIs or Windows OS services other than those described in the Metro style apps API reference. This includes APIs and services exposed by, or used to communicate with, Windows 8 desktop apps or services.

3.2 Your app must not stop responding, end unexpectedly, or contain programming errors

3.3 Your app must provide the same user experience on all processor types that it supports

If your app has a different user interface or functionality when it runs on different processor types, you must submit a separate app for each processor type and describe the differences in the Description of each app.

3.4 Updates must not decrease your app’s functionality in a way that would be unexpected to a reasonable customer

3.5 Your app must fully support touch input, and fully support keyboard and mouse input

Your app must provide visual feedback when users touch interactive elements. Your app must not use an interaction gesture in a way that is different from how Windows uses the gesture. The Windows 8 touch language is described in Touch interaction design.

3.6 Your app must use the mechanisms provided by the system for those features that have them

Your app must support a snapped layout. In landscape orientation, your app’s functions must be fully accessible when the app’s display size is 1024 x 768. Your app must remain functional when the customer snaps and unsnaps the app. Your app must neither programmatically close nor offer UI affordances to close it. Windows 8 Process Lifetime Management closes Metro style apps automatically. Your app must suspend and resume to a reasonable state. If your app implements an app bar, that bar must show up with a bottom-up swipe. If your app implements a navigation bar, that bar must show up with a top-down swipe.

3.7 Deleted

See Revision history.

3.8 Your app must meet the basic performance criteria on a low-power computer

The app must launch in 5 seconds or less
The app must suspend in 2 seconds or less

Low-power computers are described in How to test your app with the Windows App Certification Kit.

4. Metro style apps put the customer in control

4.1 Your app must obtain opt-in or equivalent consent to share personal information

Your app can publish a customer’s personal information to a service or other person only after obtaining opt-in consent. Opt-in consent means the customer gives their express permission for the requested activity, after you have: a) Described to the customer how the information will be used or shared; and b) Provided the customer a mechanism through which they can later rescind this permission and opt-out. If your app publishes a person’s personal information, but that person is not a customer, you must obtain express written consent to publish that personal information, and you must permit the person whose information is shared to withdraw that consent at any time. Personal information includes all information or data that is associated with an identifiable person. Examples of personal information include: contacts, photos, phone number, SMS or other text communication, images of the computer’s desktop or screen shots, browsing history, and other internet settings. If your app collects personal information, you must have a Privacy Policy and add a link to it in the Description page to let your customers know how you will safeguard their personal information.

4.2 Your app must respect system settings for notifications and remain functional when they are disabled

This includes the presentation of ads and notifications to the customer, which must also be consistent with the customer’s preferences, whether the notifications are provided by the Windows Push Notification Service or any other service. If a customer disables the notification function, either on an app-specific or a system-wide basis, your app must remain functional.

4.3 Your app must not jeopardize or compromise the security or functionality of the Windows system

Additionally, the app must not include, link to, distribute through the Windows Push Notification Service, or otherwise provide an entry point for viruses, malware, or any other malicious software, to access the customer’s Windows system. The Windows system includes the computer running Windows, any software running on that computer, and any computers or software communicating with that computer.

4.4 Your app must not be designed or marketed to perform, instruct, or encourage tasks that could cause physical harm to a customer or any other person

We would consider an app that allows for control of a device without human manipulation, or that is marketed for use to resolve emergency or lifesaving situations to violate this requirement.

4.5 Your app must protect customers from unintentional large data transfers over metered networks

When operating over a metered network, your app must offer the customer the option of permitting these transfers without limit or limit audio and video transfers to these data rates: · Video streams, which include download-only and two-way video messaging, must use an adaptive bit-rate technology and limit the transfer rate to no more than 256 Kbps. · Audio streams, which include voice over IP (VOIP), must limit the data rate to no more than 64KBps. When the customer’s computer is connected to a metered network, your app must obtain permission from the customer or wait until it has access to an unrestricted network before it performs any synchronization, upload, or download that requires a total transfer larger than Windows.Networking.Connectivity.DataPlanStatus.MaxTransferSizeInMegabytes. When the customer’s computer is operating outside of its home network or connected to a metered network while over the data limit, your app must obtain permission from the customer before it performs any data transfer that is larger than 1 megabyte.

4.6 Your app must comply with Windows Push Notification Service (WNS) requirements if it uses WNS notifications

If your app uses the Windows Push Notification Service (WNS) to transmit push notifications, it must do so as described in this requirement. a) You may only use WNS for apps distributed through the Windows Store. Notifications provided through WNS are considered app content and are subject to all Windows Store app policies, including the certification requirements. b) Your app must be associated with only one Package Security Identifier. c) You may not obscure or try to disguise the source of any WNS message or Package Security Identifier, or other unique referral identifier. d) You may not include in a notification any info a customer would reasonably consider to be confidential or sensitive. e) Your app must not use excessive network capacity or WNS bandwidth, or otherwise unduly burden the Windows system with WNS notifications. For example, using WNS to stream content or transfer files violates this requirement.

4.7 If you use a transaction provider other than the Store's, you must identify the provider at the time of the transaction or when it collects any payment info from the customer

If your app uses the Windows.ApplicationModel.Store namespace for in-app purchases, this messaging is provided for you. If your app uses any other method for in-app purchases or to collect payments, it must display a message to the customer stating that you are responsible for the transaction and not the Windows Store. For example, in-app purchases made from apps produced by Contoso that don’t use the Windows Store for the transaction would display a message such as, “This item is available from Contoso” at the time of the transaction.

4.8 If your app doesn't use the Windows.ApplicationModel.Store namespace for in-app purchases, your app must prompt the user for authentication to allow a transaction to be accomplished.

The app can offer the user the ability to save this authentication, but the user must have the ability to either require an authentication on every transaction or to turn off in-app transactions.

4.9 If your app collects credit card info or uses a third-party payment processor that collects credit card info, the payment processing must meet the current PCI Data Security Standard (PCI DSS)

5. Windows Store apps are appropriate for a global audience

This section describes types of content that are not permitted in the apps made available in the Windows Store. Content means the images, sounds, and text contained in the app, the tiles, notifications, error messages or ads exposed through your app, and anything that’s delivered from a server or that the app connects to. Because Windows and the apps in the Windows Store are used around the world, these requirements will be interpreted and applied in the context of regional and cultural norms.

5.1 Your app must not contain adult content, and metadata must be appropriate for everyone

Apps with a rating over PEGI 16, ESRB MATURE, or that contain content that would warrant such a rating, are not allowed. Metadata and other content you submit to accompany your app may contain only content that would merit a rating of PEGI 12, ESRB EVERYONE, or Windows Store 12+, or lower.

5.2 Your app must not contain content that advocates discrimination, hatred, or violence based on membership in a particular racial, ethnic, national, linguistic, religious, or other social group, or based on a person’s gender, age, or sexual orientation

5.3 Your app must not contain content or functionality that encourages, facilitates or glamorizes illegal activity

5.4 Your app must not contain or display content that a reasonable person would consider to be obscene

5.5 Your app must not contain content that is defamatory, libelous or slanderous, or threatening

5.6 Your app must not contain content that encourages, facilitates or glamorizes excessive or irresponsible use of alcohol or tobacco products, drugs or weapons

5.7 Your app must not contain content that encourages, facilitates or glamorizes extreme or gratuitous violence, human rights violations, or the creation or use of weapons against a person or animal in the real world

5.8 Your app must not contain excessive or gratuitous profanity

6. Windows Store apps are easily identified and understood

6.1 Your app must have a unique name

Your app’s name is what we use to list your app in the Windows Store. You must give your app a name that is unique throughout the Windows Store catalog. You can give your app a name in another language; but additional names must also be unique throughout the Store.

6.2 Your app must have a Windows age rating, and you must submit third-party ratings for your app if you have them

You must assign a Windows Store age rating that most accurately matches your app. The Age rating page contains more detailed descriptions of the content that is suitable for each Windows Store age rating. If a rating under any particular rating system is required by law in any country, you must include the rating documentation for that rating system along with your app. If your app is rated by an optional ratings board that is identified in Rating boards for Windows apps, you must also submit that ratings certificate for the app and provide the appropriate content descriptors. If your app has any existing third-party rating, the Windows Store age rating for the app must be determined from the following table. If your app has rating board ratings that correspond to different Windows Store age ratings, you must assign the Windows Store age rating that corresponds to the older audience. Apps with a rating over PEGI 16, ESRB MATURE, or a corresponding rating under other ratings systems, are not allowed.

Windows Store Age Rating	PEGI	ESRB	CERO	GRB	USK
3+ Suitable for all ages	PEGI 3 PEGI 4 in Portugal	EARLY CHILDHOOD	A (all ages)	A (all ages)	USK ab 0
7+ Suitable for ages 7 and older	PEGI 7 PEGI 6 in Portugal	EVERYONE			USK ab 6
12+ Suitable for ages 12 and older	PEGI 12	EVERYONE 10+	B (12+)	12+	USK ab 12
16+ Suitable for ages 16 and older	PEGI 16	TEEN MATURE	C (15+) D (17+)	15+	USK ab 16
Adult content Note Adult content is not allowed in the Store.	PEGI 18	ADULT	Z (18+)	18+	USK ab 18

6.3 You must provide technical support info for your app

We don’t provide customer or technical support for your app. You must provide that support and specify easily discoverable and accurate technical support info for your app in the Support contact info field of the Description. If your app requires authentication, such as a user or account name and password, you must provide a retrieval mechanism for account info—for example, through a secondary email account or phone support—and respond to customers within 24 hours.

6.4 You must list your app in at least one of the Windows Store's geographic markets

Pick the markets in which you want to list your app on the Selling details page from the Submit a new app option in your Dashboard. This is separate from and unrelated to the languages that your app supports. We will detect the languages that your app supports by reading the Package/Resources element of the app manifest when you upload the app’s package(s).

6.5 You must localize your app for all languages that it supports

At least one of the languages your app supports must be one of our certification languages. In addition, you must provide a complete description of your app for your customers in each language that you declare in your app's package. The languages that the Windows Store supports are listed in App languages. The elements of your app's description, such as screenshots, text, and promotional images must describe your app and not contain additional advertising. Tip After you upload your app’s packages, we list the languages that we detect in the Release Summary.

6.6 The capabilities you declare must relate to the core functions and value proposition of your Metro style app, and the use of those declarations must be compliant with our app quality declarations.

Learn more about our app capability declarations.

6.7 You must describe any changes to your app when you submit an update to the Store

When you submit an update to the Store, you must describe any changes in the features of the app. In addition, you must also describe any changes in the app manifest's Package/Capabilities element. These descriptions belong in the Description of update field.

6.8 You must provide at least one screenshot of your app

You must provide at least one, but no more than eight, localized screenshots of your app for each language your app supports. Each screenshot image must: · Be .png files, 1366x768 pixels in size. · Be appropriate for people as young as 12 years old. · Have a caption in the language of the description. Graphically enhanced screenshots are not allowed, unless they are clearly marked as having been enhanced.

6.9 Your Metro style app’s packages must have a correct app manifest

In each of your app’s packages, the app manifest elements must contain the correct values as described in the Package metadata requirements.

6.10 Your Metro style app’s packages must be correctly formatted

Your app’s packages must comply with the Package format requirements.

6.11 The app's category and subcategory must correspond to the character or purpose of your app

7. Desktop apps must follow additional requirements

In addition to these requirements, you must certify desktop apps under the Windows Desktop App Certification program.

7.1 The purchase page link provided for your app must send users to a location where they can directly download the app, and must not lead users to another intermediary site or a site that spoofs the purchase page

Users must be able to buy your app quickly and easily after they are directed to your purchase page from the Windows Store. You are allowed to provide two purchase page links for your app. You must use these links to provide users access to 64-bit and 32-bit versions of your app.

7.2 The information you provide to the Store about your app must match the information used on the purchase page for that app. That includes the app name, price and major and minor version numbers

Conclusion

As these requirements evolve, we’ll note the changes in the revision history here. Stable requirements are critical to your doing your best work, so we aim to ensure the changes we do make are sustainable and continue to protect and enhance your apps.

Thank you again for joining us in this commitment to delivering fantastic experiences.

Treinamento técnico em desenvolvimento de aplicações Metro Style para Windows 8

Garry Trinder — Wed, 21 Mar 2012 13:03:10 GMT

Treinamentos técnicos de Windows 8 – Aprenda & Pratique

“Nós reimaginamos o Windows”, afirma Steven Sinofsky, presidente da Divisão do Windows e do Windows Live na Microsoft.

Nestes treinamentos técnicos de um dia, você e sua equipe de desenvolvedores aprenderão a desenvolver novas aplicações para o Windows 8.

Você terá a oportunidade de ver as principais funcionalidades do Windows 8 e como utilizar o Visual Studio e o Expression Blend para desenvolver as Metro Style Apps.

Aproveite também para conhecer o time da Microsoft, apresentar sua empresa e tirar suas dúvidas.

Pré-requisitos:

1. Ter proficiência em desenvolvimento de aplicações web, particularmente HTML 5, CSS 3 e Javascript.

2. Estar inscrito no treinamento e ter recebido a confirmação de inscrição da Microsoft (veja nota baixo).

Atenção: Devido ao número limitado de vagas e alta procura por esse treinamento todas as inscrições serão submetidas a uma fila de espera. As inscrições serão aprovadas priorizando participantes que tenham preenchido a informações sobre a aplicação que pretendem desenvolver para Windows 8 e cujo desenvolvimento da aplicação esteja mais adiantado. De acordo com a demanda de cada cidade, vamos analisar a possibilidade de abrir novas turmas a partir de Abril. Importante: submeta a descrição da sua aplicação na seção Application Profile e marque a opção “I authorize Microsoft to send me communications related to this training program” para que possamos entrar em contato com você.

Links para se inscrever:

· Treinamento tecnico de Windows 8 – Aprenda
https://win8.msregistration.com/default.aspx?ID=371c8b8b-9753-4a84-bf4d-7365d38b0ccc

· Treinamento tecnico de Windows 8 – Pratique
https://win8.msregistration.com/default.aspx?ID=936f6320-8b4a-4c8f-9c52-f6003c537015

Em caso de dúvidas, envie um e-mail para Osvaldo Daibert (odaibert@microsoft.com) com o título "Windows 8 Camp".

Baixe o Windows 8 Consumer Preview e já comece a descubrir e desenvolver para o Windows 8: https://preview.windows.com

Abs,
Daibert

ATENÇÃO: MEU BLOG MUDOU DE ENDEREÇO!!!

Garry Trinder — Sat, 05 Jun 2010 12:27:42 GMT

Olá pessoal. Após 2 anos meu blog mudou de endereço. Para saber tudo sobre o Windows Server appFabric e novas tecnologias, acesse https://daibert.wordpress.com Obrigado pela audiência aqui e espero vê-los no novo blog.

Abraços,
Daibert.

Mais material de estudo para Sharepoint 2010

Garry Trinder — Tue, 27 Apr 2010 22:52:14 GMT

Olá pessoal. Segue mais uma lista de materiais para estudo de Sharepoint 2010. Os estudos de caso são bem interessante. Vale a pena gastar alguns minutos. Download SharePoint and Office 2010 – https://www.microsoft.com/2010 Case Studies Associated Press Integrates Editorial Processes using SharePoint 2007 Edelman links 3,200 Employees, 50 Million Documents, a Bowling Interest Group, and More Prepare Top 4 Things Developers Can Do to Prepare for SharePoint 2010 SharePoint 2010 Evaluation Guide and Walkthroughs for IT Professionals SharePoint 2010 Evaluation Guide and Walkthroughs for Professional Developers The SharePoint 2010 Developer Platform – An Introduction for ASP.NET Solution Architects Using Business Connectivity Services in SharePoint 2010 Learn Free resources for SharePoint developers Free SharePoint 2010 Developer Training Course Free Office 2010 Developer Training Course

Abraços,
Daibert

Windows Server AppFabric Beta 2 Refresh for Visual Studio 2010/.NET 4 RTM

Garry Trinder — Mon, 26 Apr 2010 21:03:58 GMT

Olá pessoal. Saiu hoje a versão Beta 2 do AppFabric revisada para funcionar com o Visual Studio RTM. Seguem as informações: Today we are pleased to announce a Beta 2 Refresh for Windows Server AppFabric. This build supports the recently released .NET Framework 4 and Visual Studio 2010 RTM versions—a request we’ve had from a number of you. Organizations wanting to use Windows Server AppFabric with the final RTM versions of .NET 4 and Visual Studio 2010 are encouraged to download the Beta 2 Refresh today. Please click here for an installation guide on installing the Beta 2 Refresh. We encourage developers and IT professionals building ASP.NET applications or applications that use WCF or WF and run on IIS to download the Beta 2 Refresh and provide feedback at https://connect.microsoft.com/dublin/feedback or via our forum at https://social.msdn.microsoft.com/Forums/en-US/dublin/threads/. Windows Server AppFabric is a set of application services focused on improving the performance and management of Web and Composite applications. To deliver these benefits, Windows Server AppFabric provides distributed caching technology and pre-built management and monitoring infrastructure that utilize familiar .NET skills. Currently in Beta 2, Windows Server AppFabric enhances the Application Server role in Windows Server and is available as a free download

Abraços,
Daibert

[DICA] Leituras recomendadas para quem utiliza Sharepoint 2007

Garry Trinder — Wed, 14 Apr 2010 13:55:47 GMT

SharePoint Farms Configuration and Deployment Part 3 – Development Environment
Best practices for the local, stand-alone SharePoint development environment
Creating A SharePoint Development Environment
SharePoint Solution Deployment Strategies – Dare I say Best Practices?
Building a SharePoint Development Environment
Discussão: SharePoint Patterns and Practices - General strategies on development and deployment
Best Practices Resource Center for Microsoft Office SharePoint Server 2007
TechNet: Guia para implementação de SharePoint na Internet à Internet presence scenario (Office SharePoint Server 2007) -> Internet presence scenario (Office SharePoint Server 2007)

Daibert

[DICA] Alguns Virtual Labs

Garry Trinder — Wed, 14 Apr 2010 13:05:13 GMT

Outro dia precisava de uma máquina virtual só para ver se o Biztalk 2006 tinha uma funcionalidade específica. Imaginem a preguiça de instalar toda uma infra de Biztalk só para ver uma funcionalidade? Foi então que eu me lembrei dos Virtual Labs. Eles estão meio desatualizados, mas podem ajudar bastante ainda.

Products and Technologies

Server Products

Server Technologies

Server Operating Systems

Desktop Operating Systems

Embedded Operating Systems

Windows Mobile

Security Products and Technologies

System Center Products

Office System Products

Subjects and Series

Abraços,

Daibert

Comandos básicos do AppFabric Caching

Garry Trinder — Mon, 29 Mar 2010 11:51:48 GMT

Olá pessoal. Aqui em Seattle as semanas tem sido bem puxadas, mas hoje eu consegui um tempo para um pequeno post com os principais comandos para administração do AppFabric Caching. Vale a pena destacar que o AppFAbric, em verdade, são dois produtos que AINDA estão se integrando. O AppFabric (“Dublin”) possúi uma interface de administração integrada ao IIS, assim como o WAS. Já o AppFabric Caching (“Velocity”) não possúi interface gráfica para administração e não se integra a console do IIS. Desta forma, é necessário que a administração do Cluster do cache distribuído seja feita via linha de comando PowerShell. Administrando o CacheCluster:

Start-CacheCluster
Stop-CacheCluster
Restart-CacheCluster

Administrando o CacheHost:

Start-CacheHost [-HostName] [-CachePort]
Stop-CacheHost [-HostName] [-CachePort]
Restart-CacheHost [-HostName] [-CachePort]
Get-CacheHost
a.Apresenta os “cache host servers” no cluster ativo e seus status

Administrando o Cache:

New-Cache –CacheName
Remove-Cache –CacheName
Get-Cache [-HostName] [-CachePort]
a.Apresenta a lista de caches e regions em um cache host específico
b.Se nenhum HostName e CachePort for passado como parâmetro, será apresentado a lista de todos os hostnames no cluster
Get-CacheStatistics –cacheName
a.Apresenta os status do cache como tamanho, número de itens

Se você quiser ter mais informações sobre o comandos possíveis via PowerShell, digite Get-CacheHelp na linha de comando. Para conhecer melhor a administração do AppFabric via PowerShell, acesse este link: Cache Administration with Windows PowerShell https://msdn.microsoft.com/en-us/library/ee790886.aspx Abraços,

Daibert

Windows Server AppFabric Beta 2 disponível!!

Garry Trinder — Wed, 03 Mar 2010 09:28:51 GMT

Olá pessoal. Saiu o Windows Server AppFabric Beta 2 no site do MSDN. Segundo o próprio time de produto, este Beta 2 cobre todas as funcionalidades que a versão 1.0 trará. “This build represents our “feature complete” milestone. That is, it contains all the features that we plan to ship in Windows Server AppFabric v1 by Q3 of 2010.” Estas são as novidades do AppFabric Beta 2:

For Monitoring, now when an application is configured at the Health Monitoring level (the default level) the Event Collector aggregates the WCF Operation Completed events instead of writing the individual events to the database. The OperationCompleted event is the most common event because it is fired whenever a WCF call succeeds. The Event Collector now aggregates these events that it receives over a 10 second window. It groups the OperationCompleted events by virtual path and operation name and records one AggregateOperationCompleted event instead of the raw OperationCompleted events. You can disable the aggregation at the Health Monitoring level by changing a flag in the Event Collector’s configuration file. The Release Notes document explains how to do that.
On the Dashboard in IIS Manager you will still see the total count of completed calls. However, when you drill into the Tracked Events page you’ll see the AggregateOperationCompleted events, assuming that you’re looking at an application set to the Health Monitoring level. On this page we have added “Operation Name” and “Call Duration (ms)” columns when WCF events are shown. The individual call duration or the average duration property, depending on whether the event is raw or aggregated, is shown in the “Call Duration (ms)” column.
Windows Server AppFabric now takes advantage of three new WCF events that are available for custom tracing—a user defined information, user defined warning, and user defined error event. There is a sample posted at https://msdn.microsoft.com/en-us/library/ee667248(VS.100).aspx that shows how to emit these events from your WCF service. In the AppFabric Dashboard in the WCF Calls section we’ve made the Errors header more general to include Service Model errors and any user defined errors that your services emit. On the Tracked Events page we show all three types of user defined events, with the name of the event that you’ve defined (suffixed with the actual event type name in parentheses) shown in the Event Type column.
In IIS Manager we now fully support the “tagless service” feature that .NET 4 provides. This feature allows you to omit explicit service definitions in the web.config files for WCF or WF services. When there is no tag the runtime makes some assumptions about your service—it applies default endpoints and the “nameless” (name=“”) behavior configuration. See https://msdn.microsoft.com/en-us/library/ee354381.aspx for more details.
The Endpoints list in IIS Manager now shows you the endpoints that are explicitly defined inside tags in your web.config files and also those that are applied by the runtime. This includes the service endpoints for tagless services and the standard endpoints (like the MEX endpoint and the workflow control endpoint).
The application and service configuration modules in IIS Manager now support “behavior merge”. This .NET 4 feature merges the configuration for the nameless behavior across various scopes in the IIS tree. For example, when you install Windows Server AppFabric we create the nameless behavior at the root of your server (in the web.config file inside the .NET configuration files directory). In that behavior we enable monitoring at the Health Monitoring level. This means that any service on the machine (as long as it does not use a named behavior configuration) will get this behavior by default. If you want a particular application to use a different monitoring level you can use the configuration tools (in IIS Manager or PowerShell) to change the configuration for that application. When the tools write the configuration change into the application’s web.config file they write a local nameless behavior that contains only the different monitoring setting. At runtime the system level nameless behavior gets merged with the local one defined at the application level. The net effect is that your application gets all the system defaults + the different monitoring level.
In .NET 4 some changes were made to how workflow persistence is configured. Some of the settings (like “Unload instances when Idle” and “Action on Unhandled Exception”) were moved from the instance provider behavior to separate host-related behaviors. The IIS Manager configuration tools have been updated accordingly. You will see that some of the settings that were under the “Workflow Persistence” tab in Beta 1 have been moved to a “Workflow Host Management” tab.
We replaced the System Services, Persistence Databases, and Monitoring Databases modules in IIS Manager with a Configuration wizard. As before, you use the Setup wizard to select which features you want to install. The features are grouped into a “Runtime Features” category and an “Administration Tools” category. When it has finished, the Setup wizard launches the Configuration wizard, but you can also run the Configuration wizard whenever you want to change your monitoring, persistence, or cache settings.

Novas funcionalidades do AppFabric Distributed Cache (“Velocity”) include:

We have added PowerShell cmdlets for configuring cache clusters. The commands are New-CacheCluster, Add-CacheHost, Get-CacheClusterInfo, Register-CacheHost, Remove-CacheCluster, Remove-CacheHost, and Unregister-CacheHost. These commands give you granular control of cluster deployment.
The Cache service now throttles when it is under memory pressure. When it is in the throttling state the service will allow all “read” and “delete” requests but will reject all “write” and “update” operations. This prevents the service from engaging in excessive paging. Throttling events get logged to the Event Log and allow administrators to free available memory, add nodes to the cluster, or change the expiration or deletion policy of cached items, for example.
The Cache service now logs information to two ETW channels. The Admin channel is enabled by default and collects all events like Start Cache Service and Stop Cache Service and any unhandled exceptions. The Operational channel is disabled by default. When it is enabled it captures all warnings from the Cache service. The Event Viewer shows the collected data under Applications and Services Logs -> Microsoft -> Windows -> Application Server – System Services.

A dica é baixar, testar e mandar o feedback para o time de produto no link https://connect.microsoft.com/dublin/feedback Por enquanto é só.

Abraços,
Daibert

Managed Services Engine – MSE - Um ESB gratúito da Microsoft

Garry Trinder — Tue, 15 Dec 2009 09:53:28 GMT

Olá pessoal. Neste post vou apresentar o Managed Services Engine, um Service Bus Open Source e gratuito criado pela Microsoft. O MSE surgiu da necessidade de uma série de clientes da consulturia da Microsoft em Virtualizar, Versionar e Gerenciar seus serviços já existentes. O MSE ajuda as empresas a:

Reduzir o tempo de desenvolvimento e publicação de Serviços dimunuindo o time-to-market de novos Serviços.
Versionar Serviços.
Gerenciar politicas de acesso e autorização a Serviços.
Disponibilizar sistemas legados como Serviços.
Criar uma Governança de Serviços

Arquitetura Lógica do MSE

Um ponto que deve ficar claro é que o MSE não hospeda os serviços, ele simplesmente é um um “roteador” para os serviços físicos. Porém, ele permite que uma série de atividades sejam realizadas antes da chamada ao serviço físico. Sua arquitetura é composta de três componentes lógicos: Messager: É a primeira camada da arquitetura do MSE. Ele é responsável por expor os endpoints, receber as chamadas dos serviços e executar todas as tarefas no nível da mensagem como transformação de formatos. Broker: Segunda camada da arquitetura do MSE responsável por controlar as funcionalidades do serviço, validação das chamadas, contexto dos serviços e aplicar as politicas necessárias a chamada do serviço. Dispatcher: A camada “mais baixa” do MSE. Ela é responsável por identificar através do formato da mensagem recebida, qual é o serviço físico que deve ser chamado. Com isto, em função da mensagem recebida, um versão específica de um serviço será chamada.

Arquitetura Física do MSE

O MSE foi construído utilizando .Net Framework 3.5 e WCF. Por ser um produto Open Source, ele vem com o código fonte. O único componente que não vem com o código fonte é o Runtime do MSE. Isto se deve ao fato de que o Runtime do MSE é construído em cima de componentes do Biztalk, e por uma questão de licenciamento, não foi liberado seu fonte. Service Catalog: Armazena os metadados dos serviços virtualizados. Fisicamente estas informações são armazenadas em um banco de dados SQL Server e são expostos para os outros componentes do MSE via WCF. MSE Runtime: É o componente chave da solução. É ele que possúi a lógica para virtualizar os serviços físicos. MSE Model Viewer: É uma interface gráfica feita em Windows Presentation Foundation – WPF – que permite gerenciar toda a infra-estrutura de serviços expostas no MSE. O MSE é uma solução muito robusta e escalável. Podemos ir de um modelo de topologia Single Server: Até uma topologia complexa com vários nós de componentes Messengers, Balanceamento de carga e alta disponibilidade. Futuramente pretendo falar um pouco mais detalhadamente sobre a parte de escalabilidade do MSE.

FAQ:

E o AppFabric (“Dublin”), como fica? Bom, você deve estar se perguntando aonde o “Dublin” ou o AppFabric se encaixa cenário, não é? Pois bem. O AppFabric (“Dublin”) é um host de serviços para WCF e WF, ele NÃO versiona nem virtualiza os serviços hospedados. O MSE serve para cubrir esta falta no AppFabric. Eles não são concorrentes, são complementares. Posso Versionar / Virtualizar serviços da Núvem, .Net Services? Sim. Você pode utilizar o MSE para virtualizar serviços em geral como abaixo: Posso Versionar / Virtualizar serviços Java? Sim. Como dito, o MSE não hospeda o serviço, ele é ESB, e por isso permite que serviços padrão WS-* sejam publicados nele. A Microsoft dá suporte ao MSE? Sim. Através do contrato Premier da Microsoft é possível ter suporte ao produto. A Microsoft pretende continuar evoluíndo o produto: Sim. O MSE possúi duas formas de utilização. Você pode baixar e instalar / configurar o produto por conta própria ou contratar a Microsoft Consulting Services para fazer isto para você. Com isto, existe um plano de evolução do produto que hoje se encontra na versão 7.5. Para mais informações: Microsoft Services – SOI O MSE é uma solução escalável? Sim. Como mostrado na arquitetura física podemos ir de um simples servidor até uma topologia complexa com balanceamento de carga, cluster geográfico e alta disponibilidade. Para conhecer mais: https://www.codeplex.com/servicesengine Abraços,

Daibert