What is wrong with the following code. When i try to access Retrive() operation the application time outs and at times it get communication error while MyOperation1() and MyOperation2() are working fine. host and clients are on the same machine.

using System;

using System.ServiceModel;

using System.Collections.Generic;

using System.Runtime.Serialization;

[ServiceContract()]

public interface IMyService

[OperationContract]

string MyOperation1(string myValue1);

[OperationContract]

string MyOperation2(DataContract1 dataContractValue);

[OperationContract]

CommunicationWrapper Retrieve();

public class MyService : IMyService

public string MyOperation1(string myValue1)

return "Hello: " + myValue1;

public string MyOperation2(DataContract1 dataContractValue)

return "Hello: " + dataContractValue.FirstName;

public CommunicationWrapper Retrieve()

CommunicationWrapper wrapper = new CommunicationWrapper();

List<Object> objList = new List<object>();

string str;

try

DataContract1 dataContract = new DataContract1();

dataContract.FirstName = "Saeed";

dataContract.LastName = "Hassan";

}catch(Exception e)

str = "The method or operation is not implemented.";

return wrapper;

[DataContract]

public abstract class BaseClass

private string primaryKey;

[DataMember]

public string PrimaryKey

get { return primaryKey; }

set { primaryKey = value; }

[DataContract]

public class DataContract1 : BaseClass

string firstName;

string lastName;

[DataMember]

public string FirstName

get { return firstName;}

set { firstName = value;}

[DataMember]

public string LastName

get { return lastName;}

set { lastName = value;}

[DataContractAttribute]

public class CommunicationWrapper

private List<object> bolist;

[DataMember]

public List<object> Bolist

get { return bolist; }

set { bolist = value; }

public List<object> GetBOList()

return Bolist;

public void SetBOList(List<object> value )

Hi

Ive been happily using August CTP (been too busy to upgrade!) with no problems, I tried December CTP but have problems with documenting several assemblies because they result in a command that must breach the 260 characters path limit, but I dont get this issue with the August CTP.

I'm not too familiar with exactly what happens during the whole documenting process yet but I'm including a snippet from the log file from both CTPs in the hope that someone might spot something which may help me out.

From August CTP doc build (works fine):

Info: Building topic P:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.Properties
Info: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.Reset(System.Configuration.ConfigurationElement)
Info: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.SetAttributeValue(System.String,System.String)
Info: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.Unmerge(System.Configuration.ConfigurationElement,System.Configuration.ConfigurationElement,System.Configuration.ConfigurationSaveMode)

The same section when I use Dec CTP:

Info: BuildAssembler: Building topic T:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData
Info: BuildAssembler: Building topic Overload:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.#ctor
Info: BuildAssembler: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.#ctor
Info: BuildAssembler: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.#ctor(System.String,System.Type)
Info: BuildAssembler: Building topic P:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.Attributes
Info: BuildAssembler: Building topic M:Exchange.EnterpriseLibrary.Caching.Configuration.CustomCacheStorageData.Exchange#EnterpriseLibrary#Common#Configuration#IHelperAssistedCustomConfigurationData{Exchange#EnterpriseLibrary#Caching#Configuration#CustomCacheStorageData}#BaseGetPropertyValue(System.Configuration.ConfigurationProperty)

Unhandled Exception: System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

As you can see, the bit in red is more than 260 characters hence the error, there is no path information here so I cant truncate it in any way by reducing the path on disk.

I would also like to be able to try the November CTP to see if I get the same issue, but I cant find a link to previous CTP's anywhere, can anyone provide me with this also

I'm trying to decide what might be the best way to cycle through a series of individual images or frames to give the impression of animation - similar to how an animated gif file works.

I have yet to find a single example of this kind of keyframe animation within WPF. There are probably various ways one could acheive this but I wondered if anyone could point me to an existing example using either XAML or code.

I'm currently thinking along the lines of finding a way to change the ImageSource of an ImageBrush at regular intervals - but is there a better way

Can anybody help me with EmbossBitmapEffect

After export XAML from GD some Paths with embossing convert to png, and emboss live many Paths.

"In XAML" I found EmbossBitmapEffect but can create cool emboosing :((

Can you give me some samples of EmbossBitmapEffect

Thx

I need to generate documentation in spanish. How can I change the lenguage I'm using VS2005 in spanish and framework 1.1 in spanish too.

The Code Generation Network is organizing a new conference themed around Code Generation tools and technologies to take place in Cambridge, UK from 18th May - 20th May 2007.

We're looking for session proposals from people who have experience applying DSLs, and can lead a session on this subject for a developer audience. Accepted session leaders will have their conference fees waived.

There's more information at the Code Generation 2007 web site. It's straightforward to submit a session proposal, but the submission deadline is Friday January 12th 2007.

Microsoft are sponsoring the event and I expect the DSL team to participate, so it will also be a great opportunity to talk about the tools with the experts.

We're building a web application that is using an application server via WCF web services. The web server is placed in a temporary DMZ with its own rather slow broadband connection serving traffic from the internet, while the application server is to be placed in our ordinary network behind our ordinary firewall. In other words, connections between the two servers will go through the internet with all the trouble that may cause. In about a year or so we will establish a proper DMZ to obtain a more stable and fast connection.

We have chosen to use the generic ChannelFactory class in stead of building client proxies, as this seems to be a more maintainable approach in this case.

When debugging, we have noticed that the ChannelFactory.Close() sometimes takes a little time. Some bright head came up with the idea to use the async approach in stead, by calling ChannelFactory.BeginClose(null, null), which means we initiate a close and do not wait or handle the callback by provide a delegate.

This seems to work out fine in our small test environment. My question is whether this approach is at all advisable, or might cause problems in a production environment with much heavier load.

Thanx in advance for any advice on this!

:) Helge K

Hi,

I found that if you use an ElementHost on a Win form to host a xaml aplication you will not be able to use embeded resources.

This is because the only way that WPF embed's a resource on to an .exe or .dll is by defining a <resource/> on the "app.xaml" page.

So when you use an ElementHost that merely shows a simple WPF form with some images or whatever, the only way to access resources is by accessing them thru siteoforigin URI e.g "pack://siteoforigin:,,,/XamlResources". This means you have to create a folder on your aplication to store all your resources. In my case that's bad :(.

Anyone with the same problem