Web Client Software Factory

NEW POST: Simple WCF Call inside a Module

dabasejumper — Tue, 13 May 2008 12:50:23 GMT

Thanks for the reply Bill. No I didn't. I do have a reference in the service to CompanyName.Mig.Security but that's not what I think is happening.

The problem I think is with the Development Web Server included with Visual Studio 2008 (Cassini???). Anyways, I have the WCF service hosted in another Virtual Directory in IIS on XP. When I debug my app using another Virtual Directory in IIS; everything runs fine, but when I debug with the Dev Server it gives me the error above. It's not a huge workaround, but I would still like to know what's causing the issue.

Thanks,
Mike Kushner

NEW POST: Objects are shared among all requests

Zack123 — Tue, 13 May 2008 11:20:17 GMT

Hi,

I have done a bit of reading on this and am still confused on a few points, maybe more to do with Threading and ObjectBuilder than the WCSF though.

In the sample apps you use the ServiceAgent pattern and use an IServiceAgentProxy to wrap the web reference. In the implementation of the methods you call Service.DoWork();
Is that method call thread safe or do we need to wrap it with attribute [MethodImpl(MethodImplOptions.Synchronized)] to lock the method? Similarly do the Translators that we write need to be locked when using the IEntityTranslatorService service?

Also we have a service method with a signature like so; void DoWork(string p, string p1, out string p3). Would such a call be thread safe considering again that the serivce class does not have any statics or properties and the method only calls a service proxy and acts on the results?

Also, is it ok to new up a member proxy in the constructor of an ServiceAgent and then use that member for the life time of the singleton? This would mean that multiple methods on mulitple threads would be accessing the member proxy. An example of this is in the AccountServiceAgent.cs in the global bank sample.

Many thanks for any help and advice.

Zack

NEW POST: Interfaces on Business Modules

rasane_s — Tue, 13 May 2008 05:29:59 GMT

Cool BillKrat. Thanks for answering the part of my question about: "what is the purpose of <BusinessModule>.Interface".

The explanation you give was my suspicion too, but when I use the recipe to create a business module, it does not automatically put the interface classes it builds in to the interface project. This is what confused me. So now from your answer I understand that the interface classes should be put in to the <BusinessModule>.Interface project- in my example that would mean

I<BusinessModule>Controller
I<ViewName>View (many of this, as many views)

I understand that the value is really when there is a possibility of circular reference, which in my case is not happening yet, but sounds like the best practice answer when I construct using the recipe with a Interface project, should have put the interfaces in the interface project. Please reply if the above understanding is incorrect.

The second part of my question is why does the View hold a reference to a concrete Presenter class? The more i think of it, right now it sounds academic.

NEW POST: Simple WCF Call inside a Module

BillKrat — Tue, 13 May 2008 04:03:00 GMT

Does anyone have any ideas? Thanks in advance.

Did you call your project security? This would account for this error...

NEW POST: Interfaces on Business Modules

BillKrat — Tue, 13 May 2008 03:38:50 GMT

rasane_s wrote:
So not sure about the inteface project.

Consider the following code where my BusinessModule1 has an Interface as well as a class that implements it - the class utilizes a class in FoundationModule1:

namespace BusinessModule1
{
    Interface IMyClass
    {
        string HelloWorld();
    }

    public class MyClass : IMyClass
    {
       public string HelloWorld()
        {
            // This will require a reference to FoundationModule1
            UseFulUtility uu = new UseFulUtility();

            // Get the ReturnWorld value and append to hello
            return string.format("Hello {0}", uu.ReturnWorld());
        }
    }
}

FoundationModule1 is happy but then a new requirement arises (ReuseHelloWorld) that would have us implement IMyClass in BusinessModule1 - we have a problem because BusinessModule1 references FoundationModule1 (for UseFulUtility).   We either have to copy the IMyClass interface into this project -or- refactor code to make it work.

namespace FoundationModule1
{
    public class UseFulUtility
    {
        public string ReturnWorld() { return "World"; }
    }

    // The following class would require a reference to
    // BusinessModule1 which is illegal because BusinessModule1
    // already has a reference to this module for UseFulUtility.
    public class ReuseHelloWorld : IMyClass
    {
         // Circular reference error trying to add BusinessModule1 to access IMyClass
    }
}
}}

The solution is to put your interfaces in a separate project, i.e., <BusinessModule>.Interface, and have both BusinessModule1 and FoundationModule1 reference it.

NEW POST: Interfaces on Business Modules

rasane_s — Tue, 13 May 2008 00:12:26 GMT

Hi,

When I use the recipe to create a new Business Module and check the "interface" option I get projects like
<BusinessModule>
<BusinessModule>.Interface

But always, the <BusinessModule>.Interface project is empty. Even the interfaces in the business modules are not placed in the <BusinessModule>.Interface project. Why is that so? What is the purpose of creating this interface project?

Any pointers?

I assumed that the View will have CPresenter<Iinterface> myPresenter reference by using the Interface project, but the view actually holds a concrete ref to the C<blah>Presenter class.. So not sure about the inteface project.

Regards,
rasane

NEW POST: caching recommendations & code samples

seankerr — Mon, 12 May 2008 22:35:58 GMT

Hi pbolduc,

What would you change? This is my first time using the patterns and I would appreciate any advice that you might have.

Sean

pbolduc wrote:
Looks reasonable. Not sure if it was intentional, but I noticed you do not set your callback handler, CacheItemRemovedCallback onRemove. Also, the call back is used to notify an item been removed already, not to tell you that you should remove it.

seankerr wrote:
Hi There,

Thanks for the posts they were extremely helpful. I came up with the following based on the other posts I read. I tried to take into account the questions you posted. Any more advice / help on my implementation would be appreciated.

Sean

NEW POST: Can't find Microsoft.Practices.PageFlow.dll

bschwehn — Mon, 12 May 2008 19:58:25 GMT

Thanks Ezequiel, I was just looking for the same thing! Ben

UPDATED WIKI: Home

mconverti — Mon, 12 May 2008 17:34:46 GMT

The Web Client Software Factory (WCSF) provides a set of guidance for architects and developers building enterprise Web applications. The factory includes samples, reusable code and a guidance package which automates key development tasks from within Visual Studio.

Using the Web Client Software Factory assets, developers can create Composite Web applications composed of independently developed and deployed modules. These modules are dynamically brought together at runtime into a common shell. Additionally the factory includes support for ASP.NET AJAX thus providing users with a richer and more responsive user experience.

Getting Started

The Getting Started provides recommendations on how to quickly use the guidance available in this factory.

Click here to download the Web Client Software Factory - February 2008
Click here for detailed instructions on Installing the factory or Upgrade From Previous Releases.
Click here if you want to download the Web Client Software Documentation instead of the entire factory.
Click here for a list of Known Issues.

Where to go next?

Action	Link
Read about the February 2008 release of the factory	WCSF MSDN Landing page
View our bundle catalog	Guidance Bundle catalog
View recent announcements for the Web Client program	Announcements
See a list of resources for getting started with WCSF	Learning Resources
Explore our compilation of Web Client tips, tricks and guidance from the Web Client team and the community	Knowledge Base
Read blog postings from the team	Team Blogs
Read blog postings from the trenches	Community Blogs
View Community work items that have been resolved with WCSF February 2008 release	Resolved items
View additional links and resources	Other links
View known issues	Known Issues

Participation

The factory is developed using the open process used by patterns & practices for all of its deliverables. This process includes frequent builds and releases in this community of code and documentation. If you find bugs or want additional capabilities addressed by the team, use the Issue Tracker to create a new Work Item.

You can influence this project. Please send us feedback!

Our team will continuously monitor the forums in this site to get feedback on content and to help us prioritize.

Thanks!
p&p Client Team

NEW POST: caching recommendations & code samples

pbolduc — Mon, 12 May 2008 15:18:44 GMT

Looks reasonable. Not sure if it was intentional, but I noticed you do not set your callback handler, CacheItemRemovedCallback onRemove. Also, the call back is used to notify an item been removed already, not to tell you that you should remove it.

NEW POST: caching recommendations & code samples

seankerr — Mon, 12 May 2008 02:46:59 GMT

Hi There,

Thanks for the posts they were extremely helpful. I came up with the following based on the other posts I read. I tried to take into account the questions you posted. Any more advice / help on my implementation would be appreciated.

Sean

#region Fields
        private CategorieService _controller;
        CacheItemRemovedCallback onRemove = null;

        private IHttpContextLocatorService contextLocator;
        private IList<WellcomRepository.BusinessEntities.Categorie> lstGenders;
        #endregion

        #region Properties
        private IHttpContext Context
        {
            get { return contextLocator.GetCurrentContext(); }
        }
        #endregion

        #region public Methods
        [InjectionMethod]
        public void InitializeServices([ServiceDependency] IHttpContextLocatorService contextLocator)
        {
            this.contextLocator = contextLocator;
        }

        public GendersViewPresenter([CreateNew] CategorieService controller)
        {
            _controller = controller;
        }

        public void RemoveItemFromCache(Object sender, EventArgs e) {
            if (Context.Cache["lstGenders"] != null)
                Context.Cache.Remove("lstGenders");
             }

        public override void OnViewInitialized()
        {
            if (Context.Cache["lstGenders"] == null)
            {
               lstGenders = _controller.GetGenders();
               View.lstGenders = lstGenders;

               Context.Cache.Insert("lstGenders", lstGenders, null, DateTime.Now.AddMinutes(2), Cache.NoSlidingExpiration, CacheItemPriority.High, onRemove);
            }
            else
            {
                View.lstGenders = (IList<WellcomRepository.BusinessEntities.Categorie>)Context.Cache["lstGenders"];
            }
        }

pbolduc wrote:
I would recommend adding caching at the service or controller layers. Basically, the flow is something similar to this,

[Page/UserControl] -> [Presenter] -> [Controller] -> [Service] -> [Database / Web Service]

Services are 'stateless', as they are shared for all calls, ie they are singletons. Controllers are usually created new by Presenters. Presenters are created new by Pages/UserControls.

Depending on your caching needs, you could use HttpContext.Cache or you could use the Enterprise Library caching. I would recommend Enterprise Library caching.

Also there are a few distributed caching (cache your data across multiple machines), such as NCache (check out the free version NCache Express) http://www.alachisoft.com/ncache/ or indeXus.Net Shared Cache http://www.codeplex.com/SharedCache.

Regardless of the cache you want to use, you should consider the standard caching questions such as:

What cache key are you going to use?
How long should data be cached?
How will the cache be cleaned up?

seankerr wrote:
Can anyone post code samples or recommend the approach to using caching with the WCSF?

NEW POST: Can't find Microsoft.Practices.PageFlow.dll

ejadib — Sat, 10 May 2008 20:11:23 GMT

Hi armstronga, what version of WCSF are you using? The Page Flow Application Block was removed from the latest version of WCSF and moved to WCSFContrib site. This new version of Page Flow requires Visual Studio 2008 and .NET Framework 3.5.

You can download the Page Flow Application Block from here.

Please let me know if this help you,

Ezequiel Jadib
http://staff.southworks.net/blogs/ejadib

NEW POST: Can't find Microsoft.Practices.PageFlow.dll

armstronga — Sat, 10 May 2008 16:18:12 GMT

I have the same issue as the poster above. Whilst many other "Practices" DLLs exist in that directory, the PageFlow DLLs do not!

Any others with the same issue?

NEW POST: Composite Web Application Block and Unity -- Update

MichaelPuleio — Fri, 09 May 2008 21:18:53 GMT

I'd look at what the Prism guys are doing, and hope for some inspiration.

Of course, the reason I got rid of the containers collection was that it was no longer necessary, as there are better ways to manage the containers. For things like Commands, SmartParts, Items, etc, you may need access to the collections. Of course, just because a method returns a ManagedObjectCollection does not mean it needs to store things in a ManagedObjectCollection. This could be a facade over something that plays better with Unity....

Let's move the SCSF conversations over to the other Discussion forum, in the future. I do (try to) monitor both forums (and a few others as well).

I hope that helps a bit,
Michael Puleio - patterns & practices
Blog – http://blogs.msdn.com/mpuleio/

NEW POST: Composite Web Application Block and Unity -- Update

BillKrat — Fri, 09 May 2008 19:40:42 GMT

MichaelPulio wrote
Let's roll back removing the Containers property, add the RegisterInstance and Resolve methods (that use a name) to the interface, test them, then add the CreateChildContainer method to the interface, and test it. Once we have those pieces, we can re-work ModuleLoaderService and DefaultModuleContainerLocatorService to use the new methods. Once we do all that, we can remove Containers from the ICompositionContainer interface without problems.

Do you have any high-level thoughts on how you would have approached the Containers property had it not been practical to re-work the applicable services? The reason I ask is because this won't be an option for the SCSF WorkItem (to many external components reference them)...

        ManagedObjectCollection<Command> Commands { get; }
        ManagedObjectCollection<EventTopic> EventTopics { get; }
        ManagedObjectCollection<object> Items { get; }
        ManagedObjectCollection<object> SmartParts { get; }
        ManagedObjectCollection<WorkItem> WorkItems { get; }
        ManagedObjectCollection<IWorkspace> Workspaces { get; }

NEW POST: PageFlow?

jonathan — Fri, 09 May 2008 19:30:23 GMT

The PageFlow application block was moved to WCSFContrib. You can find it here.
This version of PageFlow requires Visual Studio 2008 and .net Framework 3.5.
It includes XML PageFlow and the Guidance Package with the recipes to generate Page Flow projects and definitions.

Jonathan Cisneros
http://staff.southworks.net/blogs/jcisneros

NEW POST: caching recommendations & code samples

pbolduc — Fri, 09 May 2008 18:04:58 GMT

I would recommend adding caching at the service or controller layers. Basically, the flow is something similar to this,

[Page/UserControl] -> [Presenter] -> [Controller] -> [Service] -> [Database / Web Service]

Services are 'stateless', as they are shared for all calls, ie they are singletons. Controllers are usually created new by Presenters. Presenters are created new by Pages/UserControls.

Depending on your caching needs, you could use HttpContext.Cache or you could use the Enterprise Library caching. I would recommend Enterprise Library caching.

Also there are a few distributed caching (cache your data across multiple machines), such as NCache (check out the free version NCache Express) http://www.alachisoft.com/ncache/ or indeXus.Net Shared Cache http://www.codeplex.com/SharedCache.

Regardless of the cache you want to use, you should consider the standard caching questions such as:

What cache key are you going to use?
How long should data be cached?
How will the cache be cleaned up?

seankerr wrote:
Can anyone post code samples or recommend the approach to using caching with the WCSF?

NEW POST: caching recommendations & code samples

BillKrat — Fri, 09 May 2008 15:15:42 GMT

pbolduc provides an example here with Unit Test!
Jonathan provides an example here

Reference links pulled from a a site I'm working on

NEW POST: caching recommendations & code samples

seankerr — Fri, 09 May 2008 15:07:18 GMT

Hi There,

Can anyone post code samples or recommend the approach to using caching with the WCSF?

Sean

NEW POST: Global.asax

BillKrat — Thu, 08 May 2008 18:25:07 GMT

kdrouet74 wrote:
On Session Start I need to communicate with our business modules. How do you suggest I used the framework on Session_Start to make business layer calls? Before migrating to WCSF, I would communicate with my business proxy layer and call the necessary methods. I am trying to prevent to having the same code in different places, such as foundation module calling the business proxies and Global.asax calling the business proxies.

Is the following what you are looking for? I would recommend that you examine the WebClientApplication.cs as it also references services.

Global.asax

<%@ Application Language="C#" Inherits="Global" %>

Global.asax.cs

    public class Global : WebClientApplication
    {
        public Global()
        {
        }
 
        void Session_Start(object sender, EventArgs e)
        {
            IMyService service = RootContainer.Services.Get<IMyService>();
            Session["Message"] = service.GetHelloWorld();           
        }
 
        void Session_End(object sender, EventArgs e)
        {
        }
 
        protected override void AddRequiredServices()
        {
            base.AddRequiredServices();
            AddServiceIfMissing<MyService, IMyService>(RootContainer);
        }
        protected override void Start()
        {
        }
 
    }

IMyService.cs

    public interface IMyService
    {
        string GetHelloWorld();
    }

MyService.cs

    public class MyService : IMyService
    {
        public string GetHelloWorld() { return "Hello World"; }
    }