Hi,

as I posted in my previous email in regards Silverlight 2, I’ve decided to use ADO.NET Data Services (After consulting my mate Josh Reuben – senior SELA consultant) in order to consume the data in a very easy and light way (by using its linq notation and light weight data bandwidth using JSON).

The only main issue that I encountered with the last few days I am exploring this (new for me) technologies is the issue of cross-domain preventing:

“ADO.NET Data Services does not currently support cross-domain communications. Cross-domain communications are supported with standard REST and SOAP services, but not with ADO.NET Data Services. …… This means that a Silverlight 2 client cannot talk to services exposed through ADO.NET Data Services if those services are hosted on a different domain than the domain that hosts the Silverlight client application.”

Quoted from John Papa post here.

Recently I followed up the the Astoria blog team and found that they created a great workaround that comes to give a solution for this issue that holt me these days using these data services because my application is distributed and need to be separated for a client and server.

Find it here.

The Astoria blog team is here.

I am new to Silverlight 2 and starting these days to develop my first Silverlight application hosted on asp.net web application, which is going to be a large and complex management system for a new product of the company I am working for.

I going to use some new technologies from Microsoft house (like Silverlight, ADO.NET Data Services over WCF and Entity Framework), therefore I started to read some tutorials in regards these topics and must say that there are good tutorials on the web but I read a nice and long post: “Understanding WCF Services in Silverlight 2” that explains how to create WCF Service and more and more (which is quite basic for those that has some knowledge in WCF), but the good paragraph is the detailed info in regards the consuming this service in a Silverlight 2 application.

Check it out here.

Hi,

Long time since my last post I know, but promise to start writing again soon; I am starting these days to write my first big Silverlight 2 application, so I think I’ll have plenty of stuff to share.

For now, great and convenient search engine from google to search MSDN contents (thanks to Erez Eden, my friend that keeps me on track with such nice things…)

You can check it out in the further and save it in your favorites: http://www.google.com/microsoft

Be in touch, promise, Eran.

Long time since I spent my words here (shame on me...), but I am in a middle of a great project that touches almost every MS technology: asp.net, WPF, WCF and even WWF. I want to talk here about known issue from Microsoft and not to innovate something but to share my frustrations in regadrs it.

Even WWF is a great technology, has very intuitive API and supplies fun of programming - which is very important these days (for me at least) it has a major disadvantage: VERY VERY VERY slow VS 2008 designer. I am talking here about very big WF that contains somthing like 15 state activities, which everyone of them holds very complex conditions, code activities, send & receive activities that exposed outside as a WCF service.

In the beginning (were I was young by 6 months) life were easy and the future sound even better, but this has been changed after more and more and more logic in the WF which turned it to be a WF monster that except of doing coffee it does almost everything...

My main insight in regards to it is to split every single state (also if it very small one) to a custom activities that each one of them (of course) will be placed in a seperate file and will hold all its logic. After it, in the main workflow file you could attach each one of them and combine the puzzle.

Click to read more: VS2008 Workflow Designer is Very Slow

Hi,

ASP.NET 3.5 SP1 has browsing history (making bookmarking functional too) handling support built in.
Resently web applications become more and more ajax-style, it is important to keep that in mind and see where it is reasonable for use.

You can read about it here:http://msdn.microsoft.com/en-us/magazine/cc972638.aspx

It is a very recommended article for ASP.NET developers to read in general, It also reveals the ASP.NET v4.0 Ajax Template approach, looks really cool.

CodeRush just come out with a free version of its well known and recommended addin to VS.
It provides stronger refactoring capabilities and also ease other tasks like browsing for files in a solution.

You can check it out and some more information here: http://community.devexpress.com/blogs/markmiller/archive/2008/10/27/announcing-coderush-express-for-c.aspx

C# version is here: http://devexpress.com/Products/Visual_Studio_Add-in/CodeRushX/

Another version for ASP.NET refactoring is here: http://devexpress.com/Products/Visual_Studio_Add-in/RefactorASP/

Have fun ;)

I waited so long on regards this issue to be coming out with much more stable version, and I am not a great beleiver of beta versions but I think MVC Beta framework is kind of stable one and ready to use (I admit it my - fingers are burning in order to start working with this great tool), one more thing is that the Beta release comes with an explicit "go-live" license that allows you to deploy it in production environments.

The ASP.NET MVC Beta works with both .NET 3.5 and .NET 3.5 SP1, and supports both VS 2008 and Visual Web Developer 2008 Express SP1 (which is free - and now supports class libraries and web application project types).

You can download it from Scott Guthrie's blog here and read some more details on regards this issue.
Great examples and web casts you can find here.

My point of view on regards this issue is quite clear - I am supporting this methodology and work-scheme over the traditional asp.net webform that does simple round-trip to the server and back. One more thing is that traditional asp.net webforms were being done much more heavier and with low performance where including vast logic - not including asp.net AJAX controls (ScriptManager, UpdatePanel etc...) that make the page process to be much more slow and not intuitive;
MVC framework got me back to the traditional web development, while using simple HTML code that does simple submit to the server and shows the server-side data in fewer code while not using asp.net server controls at all.

One more great featutre that MVC supplies according to it behavior is explicit URLs patterns. This one helps to SEO against search engines - something that comes out of the box and you don't need to implement it like on regular asp.net webforms; that means MVC is perfect to content websites that suppost to be indexed by the search engines.

The main question is why Microsoft came out with this framework so lately, you know MVC methodology is exists for years...

I waited so long on regards this issue to be coming out with much more stable version, and I am not a great beleiver of beta versions but I think MVC Beta framework is kind of stable one and ready to use (I admit it my - fingers are burning in order to start working with this great tool), one more thing is that the Beta release comes with an explicit "go-live" license that allows you to deploy it in production environments.

The ASP.NET MVC Beta works with both .NET 3.5 and .NET 3.5 SP1, and supports both VS 2008 and Visual Web Developer 2008 Express SP1 (which is free - and now supports class libraries and web application project types).

You can download it from Scott Guthrie's blog here and read some more details on regards this issue.
Great examples and web casts you can find here.

My point of view on regards this issue is quite clear - I am supporting this methodology and work-scheme over the traditional asp.net webform that does simple round-trip to the server and back. One more thing is that traditional asp.net webforms were being done much more heavier and with low performance where including vast logic - not including asp.net AJAX controls (ScriptManager, UpdatePanel etc...) that make the page process to be much more slow and not intuitive;
MVC framework got me back to the traditional web development, while using simple HTML code that does simple submit to the server and shows the server-side data in fewer code while not using asp.net server controls at all.

One more great featutre that MVC supplies according to it behavior is explicit URLs patterns. This one helps to SEO against search engines - something that comes out of the box and you don't need to implement it like on regular asp.net webforms; that means MVC is perfect to content websites that suppost to be indexed by the search engines.

The main question is why Microsoft came out with this framework so lately, you know MVC methodology is exists for years...

Great post by Omar Al Zabir on regards best practices for creating websites in IIS 6.

This post will demonstrate you step by step how to make your website more scalability and cachable.

http://msmvps.com/blogs/omar/archive/2008/10/04/best-practices-for-creating-websites-in-iis-6-0.aspx