I am working with silverlight since WPF/E days and after the Silverlight 2 RTW release was wondering to my wonder tool Chiron.exe. A bit of searching took me to the blog which says:
which is available on Codeplex. So if you need/want it, there you go.
Some people were using Chiron for their automated build scenarios to
create the XAP package during the builds. A lot of the packaging stuff
for XAPs is now a part of some of the MSBuild tasks, so you can still
automate your builds using MSBuild.
That explains the stuff; i presume. I am personally missing Chiron. Silverlight DLR, ironPython is something i love and like really, however, i do not have any great ideas where i can implemnet them. So most of times its just feel good POC on SL 2 DLR.
Bottonline: I will miss you, Chiron.
The Chrome installer is trying to download itself, but the geniuses (yes, really) at google forgot to put in a password input box. Until Google releases an updated installer, you can download the full Chrome installer here:
http://dl.google.com/chrome/install/149.29/chrome_installer.exe
But my favorite remains FLOCK, Its the best!!!. I eveb blogged this using flock!!!
.NET SqlConnection object.
Data Source=ServerName; Initial Catalog=DatabaseName; Integrated Security=SSPI;
Trusted authentication uses the security credentials of the current user to make the connection to SQL Server. SQL Server uses Windows (or Active Directory) to validate the current user. ServerName can be the name of a server or the name of a SQL Server instance such as Server1\Instance2. ServerName can also be expressed as an IP address. SSPI stands for Security Support Provider Interface .
Data Source=ServerName; Initial Catalog=DatabaseName; User Id=UserName; Password=UserPassword;
In SQL Server authentication SQL Server stores the username and password. ServerName can be the name of a server or the name of a SQL Server instance such as Server1\Instance2. ServerName can also be expressed as an IP address.
Data Source=ServerName; Initial Catalog=DatabaseName; Integrated Security=SSPI; Application Name=MyAppName;
I often set the Application Name in connections strings. Whatever text you assign to Application Name will appear in a couple of different places:
Setting the application name makes it very easy to find out what applications are issuing particular SQL statements against my database. Setting the application name can also lead to an increase in the number of connections to your SQL Server. Each client that uses connection pooling will create one pool inside each application per unique connection string. If you use multiple application names you have the possibility to increase the number of pools and thus the number of connections to SQL Server. I've always found it more beneficial to have the application name than to have a few less connections to my database servers.
Data Source=ServerName; Initial Catalog=DatabaseName; Integrated Security=SSPI; MultipleActiveResultSets=True;
If you want to use MARS you'll need to enable it in the connection string.
The key characteristics of SaaS software, according to IDC, include:[3][dead link]
SaaS applications are generally priced on a per-user basis, sometimes with a relatively small minimum number of users and often with additional fees for extra bandwidth and storage. SaaS revenue streams to the vendor are therefore lower initially than traditional software license fees, but are also recurring, and therefore viewed as more predictable, much like maintenance fees for licensed software.
Wife: What the deal about multi tenancy:SaaS architectures generally can be classified as belonging to one of below Maturity levels. whose key attributes are configurability, multi-tenant efficiency, and scalability. Each level is distinguished from the previous one by the addition of one of those three attributes:
Virtualization also may be used in SaaS architectures, either in addition to multi-tenancy, or in place of it. One of the principal benefits of virtualization is that it can increase the system's capacity without additional programming. On the other hand, a considerable amount of programming may be required to construct a more efficient, multi-tenant application. Combining multi-tenancy and virtualization provides still greater flexibility to tune the system for optimal performance.[6] In addition to full operating system-level virtualization, other virtualization techniques applied to SaaS include application virtualization and virtual appliances.
If you catch an exception and the rethrow that exception using "throw;", you re-throw the exact same Exception, and the stack trace is preserved. Your Exception doesn't suffer amnesia, it remembers where it comes from.
Of course, another better known option is to wrap the caught exception in another one, using the Exception.InnerException property.
stackalloc
stackalloc allocates memory dynamically from the stack. Its very fast and the memory is reclaimed after the enclosing function exits. But it, of course, has some limitations. It only works with blittable types. It's good for arrays that will never be anything more than a few hundred kilobytes. By default, the maximum stack size is one megabyte. In practive, function call depth is very very small, unless you do something like a recursive function scanning a deep tree. Offsetting the risk that a stackalloc can generate the StackOverflowException is the infrequency of multiple dynamic stack allocations in use at the same time.
yield
yield is a common term used when referring to Iterators. The keyword can only be used in the context of an Iterator actually. Furthermore, the definition of an iterator holds the usage of yeild. Here are some definitions via MSDN.t
The volatile modifier is usually used for a field that is accessed by multiple threads without using the lock Statement (C# Reference)
statement to serialize access. See How to: Create and Terminate Threads (C# Programming Guide) for an example of volatile in a multi-threaded scenario.
default
Generally seen in generic code, the default keyword can be used to obtain the default value to a parameterized type (such as T) when you don't know some of the following:
Type Constraints
Aside from the usual keywords, there are also other concepts that may be uncommonly used. One really neat trick to generics in C# .NET 2.0 is type constraints. This is where you can take a generic type like T, and apply constraints such as the types polymorphisms and inheritance factors. We can take a simple type T, and actually require that it implements a given interface or inherits from a particular class. Even still, we can require that it has a default constructor created.
REST is an architectural style that is independent, but compatible, with XML. It’s about identifiable resources, resource representations, a fixed (uniform) interface, and linking. HTTP is REST’s most popular instantiation.
POX/HTTP means exchanging plain old XML documents over HTTP. RESTful POX, i.e. using XML in a RESTful manner, would mean POX is a subset of REST. Many, if not most POX applications don’t care about REST very much, though — they’d thus be part of a distinct set of applications.
SOAP is a standard document format for building high-level protocols. Anything that uses SOAP is (by definition) not just using plain old XML, and thus not POX; it may be RESTful, unless it violates REST principles.
HTTP requests themselves are:
WebClient
WebClient is a great API with a simple, events-based paradigm. Used to easily download a string or a Stream.
WebClient, behind the scenes, does a GET request and then gives back the result in the form required. It also automatically resolves relative URIs against the deployment URI of the XAP.
1: private void DownloadString()
Subodh Pushpak
Delhi
2: { 3: WebClient webClient = new WebClient();
4: 5: // Hook up events
6: webClient.DownloadProgressChanged += new DownloadProgressChangedEventHandler(webClient_DownloadProgressChanged);
7: webClient.DownloadStringCompleted += new DownloadStringCompletedEventHandler(webClient_DownloadStringCompleted);
8: 9: // Initiate download
10: webClient.DownloadStringAsync(new Uri("myfeed.xml", UriKind.Relative));
11: } 12: 13: void webClient_DownloadProgressChanged(object sender, DownloadProgressChangedEventArgs e)
14: { 15: // Update progress UI
16: progressTextBox.Text = e.ProgressPercentage; 17: } 18: 19: void webClient_DownloadStringCompleted(object sender, DownloadStringCompletedEventArgs e)
20: { 21: if (e.Error == null)
22: { 23: // Clear progress UI and show downloaded string
24: progressTextBox.Text = "";
25: feedTextBox.Text = e.Result; 26: } 27: } 28:
HttpWebRequest & HttpWebResponse
HttpWebRequest and HttpWebResponse are the standard .NET HTTP apis. They are much more powerful than WebClient but also more complex to use. Used to set headers or to issue a POST request.
1: private void SendPostRequest()
2: { 3: HttpWebRequest request = WebRequest.Create(new Uri("http://foo.com/upload")) as HttpWebRequest;
4: request.Method = "POST";
5: 6: // Set ContentType through property
7: request.ContentType = "application/xml";
8: 9: // Set other headers through Headers property
10: request.Headers["x-custom-header"] = "value";
11: 12: // Initiate getting request stream
13: IAsyncResult asyncResult = 14: request.BeginGetRequestStream(new AsyncCallback(RequestStreamCallback), request);
15: } 16: 17: private void RequestStreamCallback(IAsyncResult ar)
18: { 19: HttpWebRequest request = ar.AsyncState as HttpWebRequest;
20: 21: // populate request stream
22: request.ContentType = "text/xml";
23: Stream requestStream = request.EndGetRequestStream(ar); 24: StreamWriter streamWriter = new StreamWriter(requestStream, Encoding.UTF8);
25: streamWriter.Write("<?xml version="1.0"?>"
26: + "<entry xmlns="http://www.w3.org/2005/Atom">"
27: + "<author>"
28: + "<name>Elizabeth Bennet</name>"
29: + "<email>liz@gmail.com</email>"
30: + "</author>"
31: + "<title type="text">Entry 1</title>"
32: + "<content type="text">This is my entry</content>"
33: + "</entry>");
34: streamWriter.Close(); 35: 36: // Make async call for response
37: request.BeginGetResponse(new AsyncCallback(ResponseCallback), request);
38: } 39: 40: private void ResponseCallback(IAsyncResult ar)
41: { 42: HttpWebRequest request = ar.AsyncState as HttpWebRequest;
43: WebResponse response = request.EndGetResponse(ar); 44: 45: // use response.
46: } Thanks to Scorbs for such a in depth explanation, for more please visit http://scorbs.com/.
See the below three figures...
1. The ASP.NET HTTP pipeline relies on IIS to receive the request.
2. When IIS receives an HTTP request, it examines the extension of the file.
3. If the file extension is associated with executable code, IIS invokes that code, in order to process the request.
4. Mappings from file extensions to pieces of executable code (.exe) are recorded in the IIS metabase.
5. When ASP.NET is installed, it adds entries to the metabase (associating various standard file extensions, including .aspx and .asmx), with a library called aspnet_isapi.dll.
6. When IIS receives an HTTP request for one of these files, it invokes the code in aspnet_isapi.dll, which in turn funnels the request into the HTTP pipeline.
7. Aspnet_isapi.dll uses a named pipe to forward the request from the IIS to an instance of the ASP.NET worker process, aspnet_wp.exe.
8. The aspnet_wp.exe worker process uses an instance of the HttpRuntime class to process the request.
Below the diagrammatic representation of mixing Page-Events with Application-Events.
This life cycle of the ASP.NET page starts with a call to the ProcessRequest() method. This method begins by initializing the page's control hierarchy.
The life cycle of Page ends by handing off the Web page's HTML markup to the Web server, which sends it back to the client that requested the page.
| 1 | Application_Start |
| 2 | Application_BeginRequest |
| 3 | Application_AuthenticateRequest |
| 4 | Application_AuthorizeRequest |
| 5 | Application_ResolveRequestCache |
| 6 | Session_Start |
| 7 | Application_AcquireRequestState |
| 8 | Application_PreRequestHandlerExecute |
| | Page Life Cycle occurs, and at the end generated HTML is sent to the server. This HTML is then rendered by the client/browser. This is the place where the Page events mentioned at the right side of figure 2 occurs. |
| 9 | Application_PostRequestHandlerExecute |
| 10 | Application_ReleaseRequestState |
| 11 | Application_UpdateRequestCache |
| 12 | Application_EndRequest |
| 13 | Application_PreSendRequestHeaders |
| 14 | Application_PreSendRequestContent |
| | Form Displays |
Blogged with Flock
