Friday, April 30, 2010
Wednesday, April 28, 2010
Tuesday, April 27, 2010
Monday, April 26, 2010
Sunday, April 25, 2010
Saturday, April 24, 2010
Thursday, April 22, 2010
Wednesday, April 21, 2010
Monday, April 19, 2010
Saturday, April 10, 2010
Programming on Microsoft Active Directory Using Microsoft .NET Framework
Programming AD system managment tasks is still a pain with .NET, you may do this if you are developing a sophisticaed customized management tool that is not available from the suite of native tool from Microsoft.
Querying Microsoft Active Directory Using Microsoft .NET Framework Library - CodeProject
Operations on AD using DotNet
Most administrators will simply script the tools. We have a choice of using
Querying Microsoft Active Directory Using Microsoft .NET Framework Library - CodeProject
Operations on AD using DotNet
Most administrators will simply script the tools. We have a choice of using
- VB/Java scipts
- PowerShell scripting with the AD module(only for Windows 2008 R2)
- DOS shell
Friday, April 9, 2010
HTTP-Based Web Services with .NET
HTTP-Based Web Services with .NET
This is a very good and simple example of the cool stuff you can do with REST.
This is a very good and simple example of the cool stuff you can do with REST.
Learn REST: A Tutorial: 1. What is REST?
Learn REST: A Tutorial: 1. What is REST?: "1. What is REST?
REST stands for Representational State Transfer. (It is sometimes spelled 'ReST'.) It relies on a stateless, client-server, cacheable communications protocol -- and in virtually all cases, the HTTP protocol is used.
REST is an architecture style for designing networked applications. The idea is that, rather than using complex mechanisms such as CORBA, RPC or SOAP to connect between machines, simple HTTP is used to make calls between machines.
In many ways, the World Wide Web itself, based on HTTP, can be viewed as a REST-based architecture.
RESTful applications use HTTP requests to post data (create and/or update), read data (e.g., make queries), and delete data. Thus, REST uses HTTP for all four CRUD (Create/Read/Update/Delete) operations.
REST is a lightweight alternative to mechanisms like RPC (Remote Procedure Calls) and Web Services (SOAP, WSDL, et al.). Later, we will see how much more simple REST is.
Despite being simple, REST is fully-featured; there's basically nothing you can do in Web Services that can't be done with a RESTful architecture.
REST is not a 'standard'. There will never be a W3C recommendataion for REST, for example. And while there are REST programming frameworks, working with REST is so simple that you can often 'roll your own' with standard library features in languages like Perl, Java, or C#."
REST stands for Representational State Transfer. (It is sometimes spelled 'ReST'.) It relies on a stateless, client-server, cacheable communications protocol -- and in virtually all cases, the HTTP protocol is used.
REST is an architecture style for designing networked applications. The idea is that, rather than using complex mechanisms such as CORBA, RPC or SOAP to connect between machines, simple HTTP is used to make calls between machines.
In many ways, the World Wide Web itself, based on HTTP, can be viewed as a REST-based architecture.
RESTful applications use HTTP requests to post data (create and/or update), read data (e.g., make queries), and delete data. Thus, REST uses HTTP for all four CRUD (Create/Read/Update/Delete) operations.
REST is a lightweight alternative to mechanisms like RPC (Remote Procedure Calls) and Web Services (SOAP, WSDL, et al.). Later, we will see how much more simple REST is.
Despite being simple, REST is fully-featured; there's basically nothing you can do in Web Services that can't be done with a RESTful architecture.
REST is not a 'standard'. There will never be a W3C recommendataion for REST, for example. And while there are REST programming frameworks, working with REST is so simple that you can often 'roll your own' with standard library features in languages like Perl, Java, or C#."
Subscribe to:
Posts (Atom)