Category Archives: Microsoft

ASP.Net

ASP.NET Session Object

21 de Abril de 2006 – 12:08

ASP.NET provides a class called HttpSessionState, which is part of the namespace System.Web.SessionState.

Just like Request and Response objects, an HttpSessionState object is also created automatically for you in ASP.NET pages. This object is called “Session”. You can access various methods and properties of this object.
What is in a session ?

A session has several information including a session ID. Some information is created and used by the server itself. But the most important use of session is, it allows to store custom information.
You can store any key-value pairs in session.

How to store and retrieve values in ASP.NET session ?

Just like you can store values in variables, you can store values in session. Basically, you can assign values to session variables. See the following example:
The following code sample shows how to store a string value in session:
    Session(“UserId”) = “john”

In the above sample, the value “john” is assigned to a session variable called “UserId”. One important different here is, you do not declare the session variable as any datatype. Just assign any value to any session variable. The session variables will be automatically created when you simply assign values to them.
How long a session variable is valid ?

A session variable retains it’s value as long as the session is valid. Session variables are valid across all pages, as long as you access all those pages from the same browser and within the timeout period.

If you assign a value into a session variable from Page1.aspx and try to retrieve it from Page2.aspx, it will work. But if you try to access the Page2.aspx from another browser or close your original browser and open again, the session variable would have lost it’s value because a new session is created.

What can be stored in  a session? The above examples show storing and retrieving simple strings in session. But you can store complex datatypes like Dataset also into session. Many websites retrieve lot of user data from database and store into session so that it can be accessed faster from memory (session) rather than retrieving from database.

However, it is not reccommded to store lot of data into session for large websites. Session data is stored in memory and if there are thousands of online users at the same time, server may run out of memory.

Permalink | Comentários fechados em ASP.NET Session Object
SQL Server

SQL Server: TIMESTAMPS

20 de Abril de 2006 – 11:29

The SQL Server timestamp data type has nothing to do with times or dates. SQL Server timestamps are binary numbers that indicate the relative sequence in which data modifications took place in a database. The timestamp data type was originally implemented to support the SQL Server recovery algorithms.

It further states Never use timestamp columns in keys, especially primary keys, because the timestamp value changes every time the row is modified.

I’d suggest using a DATETIME or SMALLDATETIME column in this case. DATETIME columns can store dates from January 1st, 1753 through December 31st, 9999 (there’s that Y10K problem) and are accurate to roughly 3 milliseconds. They use 8 bytes of storage. SMALLDATETIME columns can store dates from January 1st, 1900 through June 6th, 2079 and are accurate to the minute. SMALLDATETIME columns only use 4 bytes of storage.

You can insert values into DATETIME columns (or SMALLDATETIME) columns by enclosing them in quotes.

INSERT Table1 (DateTimeColumn)
VALUES (‘6/3/2021’)


This will insert the date part with the time set to midnight (12:00:00 AM). You can insert the current system date and time using the GETDATE() function:

INSERT Table1 (DateTimeColumn)
VALUES ( GETDATE() )

Your SELECT statement from above might look something like this:

SELECT * FROM links WHERE gdate = ‘2000-11-05’

This will run fine if you are putting dates in with no times. If you are adding times and want all the records for a particular day you can do something like this:

SELECT * FROM links WHERE LEFT( CONVERT(varchar, gdate, 120), 10) = ‘2000-11-05’

—————————

Usando DATETIME para assumir por defeito o valor dataHora actual, pode-se colocar no DefaultValue a funcao (getdate())

Permalink | Comentários fechados em SQL Server: TIMESTAMPS
IIS

Alterando o limite de conexões ao IIS do Windows XP

19 de Abril de 2006 – 15:56

O windows XP não foi feito para servir de servidor, mas sim como máquina cliente. non entanto é frequente que se faça uso do windows XP durante o processo de desenvolvimento, então muitas vezes precisamos que o windows XP tenha um comportamento um pouco mais parecido com o de um servidor.

O IIS do windows XP vem configurado por padrão para um limite de no máximo 10 conexões simultâneas. Para algumas actividades de desenvolvimento isso pode ser prejudicial.

Podemos alterar esse limite de conexões simultâneas até um limite máximo de 40 conexões, limite definido pelo sistema operativo.

Para fazer essa alteração aceda o directório adminScripts que estará dentro do diretório do IIS (por default é c:\inetpub) e execute a seguinte instrução, via prompt :

adsutil set w3svc/MaxConnections 40

Permalink | Comentários fechados em Alterando o limite de conexões ao IIS do Windows XP
Exchange Microsoft

Pricing and Licensing for Medium Organizations

11 de Abril de 2006 – 15:30
Estimated Pricing
Exchange Server 2003 running on Microsoft Windows 2000 Server or Microsoft Windows Server 2003 requires both server licenses and client access licenses (CALs). Review the following tables to find estimated pricing information1.
Server Pricing
Products Prices Comments
Exchange Server 2003 Standard Edition $699 US The standard edition of Exchange Server 2003 is designed to meet the messaging and collaboration needs of small and medium-sized organizations. You need to purchase Exchange Server 2003 CALs in addition to a basic server license. Compare to Enterprise Edition.
Exchange Server 2003 Enterprise Edition $3,999 US Exchange Server 2003 Enterprise Edition is designed for large organizations that have the highest requirements for reliability, scalability, and manageability. You need to purchase Exchange Server 2003 CALs in addition to a basic server license. Compare to Standard Edition.
Client Access License (CAL) – User Pricing
Products Prices Comments
Exchange Server 2003 user CAL $67 US The Exchange Server 2003 user CAL is required for each user gaining access to the server and entitles access rights to both editions of Exchange Server. Each Exchange Server 2003 CAL also includes Microsoft Office Outlook 2003 or Microsoft Entourage 2004 for Mac and permits access from Microsoft Office Outlook Web Access, Outlook Mobile Access, Exchange ActiveSync, or any standard Internet-messaging client.
Exchange Server 2003 device CAL $67 US The Exchange Server 2003 device CAL is required for each device accessing the server and entitles access rights to an unlimited number of users sharing this common device. The device CAL includes Outlook 2003. An example of such a device is a kiosk running Outlook Web Access that is shared by several e-mail users.

——————————————————-
microsoft.com/exchange/howtobuy/medium.mspx

Permalink | Comentários fechados em Pricing and Licensing for Medium Organizations
Exchange Microsoft

Exchange Server 2003 Edition Comparison

11 de Abril de 2006 – 15:25

Exchange Server 2003 comes in two editions:

Standard Edition and Enterprise Edition.

•Exchange Server 2003 Standard Edition is designed to meet the messaging and collaboration needs of small and medium corporations, and for specific messaging server roles or branch offices.

•Exchange Server 2003 Enterprise Edition, designed for large enterprise corporations, enables you to create multiple storage groups and multiple databases. Exchange Server 2003 Enterprise Edition provides a 16-terabyte message store that removes the constraints on the number of users and amount of data that a single server can manage.

Both editions feature:

•Network compression. Microsoft Office Outlook 2003 is designed for optimum network performance and features attachment and e-mail body compression, fewer round trips between server and client, and more intelligent synchronization.

•Exchange Server 2003 Management Pack. Help monitor and proactively manage deployments with the Microsoft Operations Manager Management Pack.

•Integrated support for mobile devices. Get support for Windows Mobile–enabled mobile device synchronization for e-mail, contacts, and calendars plus mobile browsing capabilities.

•Volume Shadow Copy service. Use the Volume Shadow Copy service in Microsoft Windows Server 2003 to enable improved backup and restore capabilities, thereby reducing the impact to your users and increasing system availability.

•Flexible configuration. You can configure Exchange Server 2003 as a front-end server residing in either the perimeter network (also known as DMZ, demilitarized zone, and screened subnet) or behind the firewall to support multiple client types such as Outlook 2003 (using remote procedure call [RPC] over HTTP), Microsoft Office Outlook Web Access, Outlook Mobile Access, Exchange ActiveSync, Post Office Protocol 3 (POP3), and Internet Message Access Protocol (IMAP).

•Recovery Storage Group. Recover entire storage groups, databases, or individual mailboxes while minimizing impact to your users. This feature has the potential to replace the need for separate servers dedicated to recovery purposes.

Feature Standard Edition Enterprise Edition
Storage groups support 1 storage group 4 storage groups
Number of databases per storage group 1 mailbox store and 1 public folder store 5 databases
Total database size Maximum 16 gigabytes (GB) per database1 Maximum 16 terabytes, limited only by hardware2
Exchange Server clustering Not supported Supported
X.400 connector Not included Included

1 Mailbox storage size limits increase to 75 GB for Exchange Server 2003 Standard Edition with Service Pack 2.
2 Sixteen terabytes of messaging storage is beyond most organizations’ requirements to meet service level agreements for timely messaging backup and restore.

Permalink | Comentários fechados em Exchange Server 2003 Edition Comparison
Exchange Microsoft

Licence for Exchange Server 2003

11 de Abril de 2006 – 12:48

Exchange 2003 a correr em Microsoft Windows® 2000 Server ou Microsoft Windows Server™ 2003 requer licenças de Servidor e de Cliente (CALs).
mais info em Exchange 2003 Licensing FAQ.

Products Comments
Exchange 2003 user CAL The Exchange 2003 user CAL is required for each user gaining access to the server and entitles access rights to both editions of Exchange. Each Exchange 2003 CAL also includes Microsoft Office Outlook® 2003 and permits access from Microsoft Office Outlook Web Access, Outlook Mobile Access, Exchange Server ActiveSync®, or any standard Internet-messaging client.
Exchange 2003 device CAL The Exchange 2003 device CAL is required for each device accessing the server and entitles access rights to an unlimited number of users sharing this common device. An example of such a device is a kiosk running Outlook Web Access that is shared by several e-mail users.
External Connector licence The new External Connector licence (EC) is an optional additional server licence for external users that enables access to your servers running Exchange 2003. With this licence, you do not need to buy individual Exchange CALs. The EC licence is purchased for every copy of Exchange 2003 that can be accessed by the external user. An example of an external user is a person who is not an employee or similar personnel of the company or its affiliates. This licence allows access to the server running Exchange by an unlimited number of external users that can include, but is not limited to, business partners, suppliers, customers, retirees, and alumni. It is licensed per server.
Exchange 2003 Standard Edition The standard edition of Exchange 2003 is designed to meet the messaging and collaboration needs of small and medium-sized organizations. You need to purchase Exchange 2003 CALs in addition to a basic server licence.
Exchange 2003 Enterprise Edition Exchange 2003 Enterprise Edition is designed for large organizations that have the highest requirements for reliability, scalability, and manageability. You need to purchase Exchange 2003 CALs in addition to a basic server licence.
Windows Server 2003 or Windows 2000 Server1 See your local reseller to order Windows Server 2003, or visit the Windows 2003 Server Pricing and Licensing page.link

—————
microsoft.com/uk/windowsserversystem/exchange/how-to-buy.mspx
microsoft.com/exchange/howtobuy/medium.mspx

Permalink | Comentários fechados em Licence for Exchange Server 2003

Requisitos de sistema do SharePoint Portal Server 2003

11 de Abril de 2006 – 11:55

configuração de sistema recomendada para usar o SharePoint Portal Server 2003 depende de o computador estar sendo usado como servidor, como cliente de colaboração de documento ou para navegação.Você também pode ler os requisitos de sistema para o Microsoft Windows SharePoint Services.

Requisitos de sistema para o SharePoint Portal Servers
Computador/processador PC com processador compatível com o Pentium III ou superior
Memória Mínimo de 512 MB (megabytes) de RAM
Disco rígido Mínimo de 550 MB de espaço em disco disponível
Observação: Formate o disco utilizando o sistema de arquivos NTFS.
Sistema operacional Microsoft Windows Serverâ„¢ 2003 Standard Edition; Windows Server 2003 Enterprise Edition; Windows Server 2003 Datacenter Edition ou Windows Server 2003 Web Edition
Servidor Servidor de aplicativo da Web com Microsoft ASP.NET e o IIS (Internet Information Services) 6.0 com os seguintes componentes:

  • Arquivos comuns
  • SMTP (Protocolo de transferência de correio simples)
  • Serviço World Wide Web

Observações

  • É necessário executar o sistema operacional com a mesma versão e o mesmo idioma e, onde aplicável, a mesma versão e o mesmo idioma do Microsoft SQL Serverâ„¢ 2000 para todos os servidores no farm de servidores.
  • Você não pode instalar os componentes do SharePoint Portal Server 2003 com bibliotecas de documentos compatíveis com versões anteriores nos servidores utilizando: Microsoft Exchange Server, Microsoft Site Server, Microsoft Office Server Extensions (OSE), Microsoft FrontPage® Server Extensions, Web Storage System (WSS) ou Microsoft SharePoint Portal Server 2001.
Bancos de dados Microsoft SQL Server 2000 Desktop Engine (MSDE 2000); SQL Server 2000 Enterprise Edition (64-bit), mais o SQL Server 2000 SP3 ou posterior; ou SQL Server 2000, mais o SQL Server 2000 SP3 ou posterior.
Rede As configurações de vários servidores devem ser membros de domínios Microsoft Windows NT® 4.0, Microsoft Windows® 2000 ou Windows Server 2003.
Requisitos de sistema para clientes de colaboração de documentos
Computador/processador PC com processador compatível com o Pentium III de 200MHz ou superior
Memória 64 MB de RAM
Disco rígido 30 MB de espaço em disco disponível no Windows 2000 e no Windows XP; ou 50 MB no Windows 98 e no Windows NT 4.0
Observação: Formate o disco utilizando NTFS, FAT (tabela de alocação de arquivos) ou o sistema de arquivos FAT32.
Sistema operacional Qualquer versão do Windows Server 2003, mais o último service pack; Windows XP Professional, mais o SP1a ou posterior; Windows 2000 Server, mais o Service Pack 2 (SP2) ou posterior; Windows 2000 Professional ou Advanced Server, mais o Service Pack 3 (SP3) ou posterior; ou Windows NT 4.0, mais o SP6a ou posterior; ou Windows 98
Observação: Os coordenadores de Colaboração de documentos devem utilizar qualquer versão do Windows Server 2003, mais o último service pack; Windows XP Professional; ou Windows 2000 Professional, Server ou Advanced Server.
Software Microsoft Outlook® Express 5.01 ou posterior

Requisitos de sistema para navegadores
Navegador Para acessar sites de portal é necessário um dos seguintes itens:

  • Microsoft Internet Explorer 5.01, mais o último service pack
  • Microsoft Internet Explorer 5.5, mais o último service pack
  • Microsoft Internet Explorer 6.0, mais o último service pack
  • Microsoft Internet Explorer 5.2 para Mac OS X, mais o último service pack
  • Netscape Navigator 6.02 ou posterior
  • Netscape Navigator 6.2 para Mac
  • Netscape Navigator 6.2 para UNIX

A administração de sites do portal e a �rea de tópicos exigem um dos seguintes itens:

  • Microsoft Internet Explorer 5.5, mais o último service pack
  • Microsoft Internet Explorer 6.0, mais o último service pack

LINK

Permalink | Comentários fechados em Requisitos de sistema do SharePoint Portal Server 2003

Windows SharePoint Services and SharePoint Portal Server 2003

11 de Abril de 2006 – 11:54

logo sharepoint services1. O que é o SharePoint Portal Server 2003?

O SharePoint Portal Server 2003 é o servidor de portal escalonável que conecta pessoas, equipes e conhecimento por meio de processos comerciais.

O SharePoint Portal Server 2003 integra informações de vários sistemas em uma solução segura por meio de recursos de conexão simples e de integração de aplicativos comerciais. Ele fornece ferramentas de gerenciamento e implantação flexíveis e facilita a colaboração ponto a ponto por meio da agregação, organização e pesquisa de dados. O SharePoint Portal Server 2003 também permite que os usuários encontrem, de forma rápida, informações relevantes por meio da individualização e personalização do conteúdo e do layout do portal, bem como pela definição do público-alvo. A definição de um público-alvo tem como objetivo informar e atualizar indivíduos com base em sua função organizacional, participação na equipe, interesse, grupo de segurança ou qualquer outro critério de participação que pode ser definido com o uso de notificações ou do Web Parts.
2. O que é o Windows SharePoint Services? Ele faz parte do SharePoint Portal Server 2003?

O Windows SharePoint Services é o mecanismo que permite criar sites para compartilhamento de informações e colaboração de documentos. Parte principal da infra-estrutura de operadores de informação fornecida no Microsoft Windows ServerT 2003, o Windows SharePoint Services oferece funcionalidade para o Microsoft Office System e outros aplicativos da área de trabalho e funciona como uma plataforma para desenvolvimento de aplicativos.

Os sites do SharePoint fornecem comunidades para colaboração de equipe, permitindo que os usuários trabalhem juntos em documentos, tarefas e projetos. O ambiente é projetado para implantação, administração e desenvolvimento de aplicativos fácil e flexível.

3. Qual é a relação entre o SharePoint Portal Server 2003 e o Windows SharePoint Services?

O Microsoft SharePoint Products and Technologies (incluindo o SharePoint Portal Server 2003 e o Windows SharePoint Services) fornece soluções de colaboração escalonáveis com ferramentas flexíveis de implantação e gerenciamento. O Windows SharePoint Services fornece sites para colaboração de equipe e o SharePoint Portal Server 2003 conecta os sites, as pessoas e os processos comerciais – facilitando o compartilhamento de conhecimento e tornando as organizações mais inteligentes.

O SharePoint Portal Server 2003 também amplia os recursos do Windows SharePoint Services, fornecendo ferramentas organizacionais e de gerenciamento para sites do SharePoint e permitindo que as equipes publiquem informações para a organização inteira. Para obter mais informações sobre a relação entre o SharePoint Portal Server e o Windows SharePoint Services, visite a página Windows SharePoint Services and SharePoint Portal Server 2003.

4. Quais são os principais benefícios do SharePoint Portal Server 2003?

O SharePoint Portal Server 2003 foi desenvolvido com três objetivos principais: personalização, integração e colaboração. Os recursos de personalização permitem que operadores de informação e gerentes de sites criem e gerenciem sites pessoais, além de habilitá-los para pesquisa, definição de público-alvo e troca de experiência em assuntos relacionados. O SharePoint Portal Server 2003 fornece organização e integração simples de sites do Windows SharePoint Services, oferecendo um nível de descoberta e de gerenciamento em sites desconectados anteriormente dentro de uma organização. E os componentes de colaboração ampliados no SharePoint Portal Server 2003 permitem que as pessoas se conectem às informações e entre si.
5. Para quem o SharePoint Portal Server 2003 foi desenvolvido?

O SharePoint Portal Server 2003 foi desenvolvido para equipes e indivíduos em organizações de médio e grande porte.

6. Por que as organizações ou equipes devem considerar o uso do SharePoint Portal Server 2003?

O SharePoint Portal Server permite que as organizações criem e gerenciem sites pessoais e de equipe, integrem sites desconectados anteriormente, além de permitir que equipes e indivíduos colaborem mutuamente. Os clientes poderão localizar e organizar aplicativos, equipes, pessoas, bem como integrar e disponibilizar sites de colaboração de um local. Além disso, eles poderão obter acesso a informações relevantes contextualmente, incluindo Minha Equipe, Meu Site, Minhas Informações e tendo tudo isso como uma solução empresarial extensa e flexível. Os clientes também terão sites pessoais com exibições públicas e particulares; uma valiosa experiência de colaboração com integração do Office System e gerenciamento de conhecimento por meio de espaços empresariais, pessoais e de equipe.

7. Como ocorre a integração do SharePoint Products and Technologies com o Microsoft Office System?

O Microsoft Office System fornecerá uma integração significativa com o Windows SharePoint Services, permitindo que os usuários trabalhem juntos de modo mais eficiente em uma base ad hoc, utilizando sites do SharePoint e do Espaço de trabalho de documento. Eles são mostrados em um novo painel de tarefas nos documentos do Microsoft Office System.

Outros recursos incluem controle de versão, ferramentas de criação de site de Espaço de trabalho de reunião, links de dados ativos do Microsoft Office Excel 2003 e do Microsoft Office Access 2003 e compartilhamento de calendário.

8. Quais são os requisitos de sistema para o SharePoint Portal Server 2003?

Consulte os requisitos de sistema para o SharePoint Portal Server 2003.

links:

http://www.microsoft.com/brasil/office/sharepoint/faq.asp
http://www.technetbrasil.com.br/Artigos/Windows2003/FSDOCLIB/
http://www.microsoft.com/portugal/office/sharepoint/prodinfo/upgrade.mspx

Permalink | Comentários fechados em Windows SharePoint Services and SharePoint Portal Server 2003
SQL Server

SQL Server 2000 Data Types

11 de Abril de 2006 – 11:12

Built-in data types SQL Server 2000 ships with 27 built-in (system) data types

Data Types Description
bigint Integer data from -2^63 through 2^63-1
int Integer data from -2^31 through 2^31 – 1
smallint Integer data from -2^15 through 2^15 – 1
tinyint Integer data from 0 through 255
bit Integer data with either a 1 or 0 value
decimal Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
numeric Fixed precision and scale numeric data from -10^38 +1 through 10^38 -1
money Monetary data values from -2^63 through 2^63 – 1
smallmoney Monetary data values from -214,748.3648 through +214,748.3647
float Floating precision number data from -1.79E + 308 through 1.79E + 308
real Floating precision number data from -3.40E + 38 through 3.40E + 38
datetime Date and time data from January 1, 1753, through December 31, 9999,with an accuracy of 3.33 milliseconds
smalldatetime Date and time data from January 1, 1900, through June 6, 2079,with an accuracy of one minute
char Fixed-length character data with a maximum length of 8,000 characters
varchar Variable-length data with a maximum of 8,000 characters
text Variable-length data with a maximum length of 2^31 – 1 characters
nchar Fixed-length Unicode data with a maximum length of 4,000 characters
nvarchar Variable-length Unicode data with a maximum length of 4,000 characters
ntext Variable-length Unicode data with a maximum length of 2^30 – 1 characters
binary Fixed-length binary data with a maximum length of 8,000 bytes
varbinary Variable-length binary data with a maximum length of 8,000 bytes
image Variable-length binary data with a maximum length of 2^31 – 1 bytes
cursor A reference to a cursor
sql_variant A data type that stores values of various data types,except text, ntext, timestamp, and sql_variant
table A special data type used to store a result set for later processing
timestamp A database-wide unique number that gets updated every timea row gets updated
uniqueidentifier A globally unique identifier

User-defined data types

SQL Server 2000 supports user-defined data types too. User-defined data types provide a mechanism for applying a name to a data type that is more descriptive of the types of values to be held in the object. Using user-defined data type can make it easier for a programmer or database administrator to understand the intended use of any object defined with the data type. The user-defined data types are based on the system data types and can be used to predefine several attributes of a column, such as its data type, length, and whether it supports NULL values. To create a user-defined data type, you can use the sp_addtype system stored procedure or you could add one using the Enterprise Manager. When you create a user-defined data type, you should specify the following three properties:

  • Data type’s name.
  • Built-in data type upon which the new data type is based.
  • Whether it can contain NULL values.

The following example creates a user-defined data type based on money data type named cursale that cannot be NULL: 

EXEC sp_addtype cursale, money, 'NOT NULL' GO

Both system and user-defined data types are used to enforce data integrity. It is very important that we put forth a lot of effort while designing tables: the better you design your tables, the more time you can work without any performance problems. In an ideal case, you never will update the structure of your tables.

Permalink | Comentários fechados em SQL Server 2000 Data Types
ASP.Net

Handling Errors

11 de Abril de 2006 – 11:08

Quando ocorre um erro numa pagina. o ASP.NET envia informação sobre o erro para o cliente. Os erros são divididos em 4 categorias:

  • Configuration errors: Occur when the syntax or structure of a Web.config file in the configuration hierarchy is incorrect.
  • Parser errors: Occur when the ASP.NET syntax on a page is malformed.
  • Compilation errors: Occur when statements in a page’s target language are incorrrect.
  • Run-time errors: Occur during a page’s execution, even though the errors could not be detected at compile time.

By default, the information shown for a run-time error is the call stack (the chains of procedure calls leading up to the exception). If debug mode is enabled, ASP.NET displays the line number in source code where the run-time error originated. Debug mode is a valuable tool for debugging your application. You can enable debug mode at the page level, using the following directive:

>

Note: Running debug mode incurs a heavy performance penalty. Be sure to disable it before deploying your finished application.
Depending on the circumstances, you might want to handle application errors in different ways. For example, at development time you probably want to see the detailed error pages that ASP.NET provides to help you identify and fix problems. However, once an application is being served in a production environment, you probably do not want to display detailed errors to your customer clients. You can use ASP.NET to specify whether errors are shown to local clients, to remote clients, or to both. By default, errors are shown only to local clients (those clients on the same computer as the server). You can also specify a custom error page to redirect clients to if an error occurs.

---------


artigo completo aqui
Permalink | Comentários fechados em Handling Errors

« Página anterior — Página seguinte »

« Página anterior — Página seguinte »