Problem Getting Started? Ask your questions here.

Coordinator
Sep 3, 2009 at 2:29 PM

Problem Getting Started? Ask your questions here.

Sep 23, 2009 at 7:47 AM
Edited Sep 23, 2009 at 10:46 AM

Question withdrawn.

Nov 5, 2009 at 4:45 AM

Two questions:

1. How do I find out more about what settings options are available beyond what is in the help document.  I want to customize the navigation and don't know what options are available.

2. How do I make my silverlight app the full height of the browser.  I have 100% height on my object tag, but it looks to be only 200px or so high.

Thank you,
Austin 

Coordinator
Nov 5, 2009 at 1:19 PM

Hi,

To answer your first question, every available settings are listed in the settings template (delivered in our "Get Started Pack"). This pack also provide the corresponding xml schema to help any user to create easily a valid setting file.

About the size settings your code is OK but it seems that some browser doesn't support the height settings in percent with Silverlight components.  Set the height in pixel seems to be the only way to avoid this problem.

Thank you

 

Coordinator
Nov 6, 2009 at 2:16 AM

Austin - if you post your code for the Silverlight height issue, I could have a look too.

Nov 8, 2009 at 9:36 PM
Edited Nov 9, 2009 at 12:58 AM

Thanks for the responses, that helped.  I downloaded the Default Themes Source and when I tried to compile I got a "The type or namespace name "ICE" could not be found" and I noticed that the ICE reference was not connected.  Do I need a ICE.dll to build the Default Themes Source?  If so, where can I get that.

EDIT: I was able to compile the Icon Library by downloading the source for ICE, compiling it, and updating the ICE reference.  However, now when I compile my updated IconLibrary and add the dll to my project, I can't access the new styles I created.  The nodes show up as the default nodes.  Any ideas?

Thanks

Coordinator
Nov 12, 2009 at 1:09 PM

Austin - this is a compilation linking issue, so I would like you to check a few thing.

1)Make sure when you update the reference of ICE.dll you will use the Xap file of same build in your project.

2)Try this procedure without any major change (our project is in a Silverlight 2.0 version)

3) make sure the debug mode is activate and use Maj-S key to see the list of all recent error.

4) make sure that your theme reference is correct ( Namespace.Class )

Thank you for your patience.

Coordinator
Nov 12, 2009 at 2:14 PM

Austinm let me also insist on Clement's 4th point:  your XML configuration file must be changed so your node styles must correctly reference your new class name. Also turn the debug mode to 1 so that Silverlight will display any issue it find at run time.

Nov 16, 2009 at 12:57 PM

I am having a similiar problem, I cannot get any other node type to show up beside the default when I try to compile everything myself.  I am just attempting to compile everything, and use the IconLibrary.FlagNodeView node style to make sure it is working before I attempt to customize my own node style.  My nodes show up, but they are the default nodes, not the Flag ones.

I built the ICE project to get the ICE.dll and ICE.xap files.  I then built the IconLibrary project setting the reference to the ICE.dll that I built.  I then copied the IconLibrary.dll and ICE.xap file to my web folder and attempted to view my example html page, but it displays as default nodes.  My iceNodeStyle.xml is set to: <className>IconLibrary.FlagNodeView</className>

If I use fiddler, I see it pull in my settings files correctly.  I have also set <debug>1</debug> in my iceSettings.xml file, but I don't see any error message when the graph displays. 

Any help with this would be greatly appreciated. 

Thanks,

Chad

 

Nov 17, 2009 at 2:18 AM

I did the same thing as Chad with the same results.  I just compiled the ICE Source downloaded from CodePlex, updated the reference to the ICE.dll in the IconLibrary project, built the IconLibrary project as-is and then was not able to use any of the themes from the IconLibrary in my project (after pulling in the new ICE.xap and IconLibrary.dll into my project).  If I use the IconLibrary.dll and ICE.xap that comes in the ICE Starter Kit then I can use the TagNodeView and all the other themes available in the IconLibrary.  I have Silverlight 3 installed, but it seemed to upgrade everything okay.

What should I try from here?

Thanks,
Austin 

Coordinator
Nov 17, 2009 at 12:09 PM

Ok, I suppose the upgrade of the project from Silverlight SDK2 to Silverlight SDK3 changed the behavior somewhere in the code.

 

I will create a new VM to make a few test and correct the thing. If you have the time to help me, please try to run ICE in debug mode and set a breakpoint in both NodeStyle.cs constructors.

Thank you.

Nov 20, 2009 at 6:05 PM

Is it possible to get started using Visual Studion Express 2008?

Coordinator
Nov 21, 2009 at 2:57 PM

@rsanan: Haven't tried, but I don't see why not. Let us know if it worked.

Coordinator
Nov 24, 2009 at 6:07 PM

@Chad and @Austin: we havent' given up on the problem you're experiencing. I know Clement is trying to reproduce the problem you're having. You're using VS 2008 SP1 and Silverlight SDK 3, right?

Nov 24, 2009 at 6:09 PM

That is correct.  What happens when you try it under that setup?

Thank you for looking into this.

Coordinator
Nov 26, 2009 at 1:41 PM

@Chad and @Austin: I've finish my investigation. First I was thinking the issue was related to the silverlight SDK3. But after creating a new VM using VS 2008 SP1 and Silverlight SDK3 I encountered some strange downloading issues. Even with those new issues, my icons still working. So I solved those issues, but I can't reproduce your error. My custom IconLibrary.dll work just fine with both IE8 and Chrome. Are you sure you don't have any error, warning or any other clue that can help me to understand your problem??? do you compile the project under debug or Release??? 

@Herve: I will send you soon a list of file to modify. I don't have a devenv for Silverlight 2 so you will have to test it yourself. Sorry...

 

 

Dec 1, 2009 at 1:40 AM

I've tried debug and release now.  It is weird because I don't get any errors, the icons just don't show up.  If I use the IconLibrary.dll and the ICE.xap that came with the starter kit i can get those icons to work, but when I try to compile it myself it stops working...

Would it be possible for you to send me a zip of a project where you have it working so I could try to see what is different with mine?

Coordinator
Dec 1, 2009 at 4:09 PM

@Austin: No problem, just send me your e-mail with a private message and I will send you the version I'm working on.

Coordinator
Dec 12, 2009 at 9:32 PM

See if this new video tutorial I created help resolves your problem: http://www.screencast.com/t/MjU1NmYy

 

cpressler wrote:

I am having a similiar problem, I cannot get any other node type to show up beside the default when I try to compile everything myself.  I am just attempting to compile everything, and use the IconLibrary.FlagNodeView node style to make sure it is working before I attempt to customize my own node style.  My nodes show up, but they are the default nodes, not the Flag ones.

I built the ICE project to get the ICE.dll and ICE.xap files.  I then built the IconLibrary project setting the reference to the ICE.dll that I built.  I then copied the IconLibrary.dll and ICE.xap file to my web folder and attempted to view my example html page, but it displays as default nodes.  My iceNodeStyle.xml is set to: <className>IconLibrary.FlagNodeView</className>

If I use fiddler, I see it pull in my settings files correctly.  I have also set <debug>1</debug> in my iceSettings.xml file, but I don't see any error message when the graph displays. 

Any help with this would be greatly appreciated. 

Thanks,

Chad

 

 

Dec 23, 2009 at 8:28 PM

I think I figured out the problem!  I spent a couple hours just running through the ICE application to try to determine where the problem was occurring.  What I discovered was that the IconLibrary.dll I was passing was getting loaded after the NodeStyle was being created, so the IconLibrary assembly was not in the assembly list.  To fix this, I simply moved the IconLibrary.dll to the top of my InitParms list in my Silverlight object and it worked!  

So, my I changed my InitParms from looking like:

 

<param name="initParams" value="
    myFirstNode = http://localhost:55555/ICEIdeas.aspx,
    myModeFile = http://localhost:55555/xml/iceSettings.xml,
    myConstantsFile = http://localhost:55555/xml/iceConstants.xml,
    myNodeStylesFile = http://localhost:55555/xml/iceNodeStyles.xml,
    myLinkStylesFile = http://localhost:55555/xml/iceLinkStyles.xml,
    myActionsFile = http://localhost:55555/xml/iceActions.xml,
    myTheme = http://localhost:55555/IconLibrary.dll" />

 

to looking like:

 

<param name="initParams" value="
    myTheme = http://localhost:55555/IconLibrary.dll,
    myFirstNode = http://localhost:55555/ICEIdeas.aspx,
    myModeFile = http://localhost:55555/xml/iceSettings.xml,
    myConstantsFile = http://localhost:55555/xml/iceConstants.xml,
    myNodeStylesFile = http://localhost:55555/xml/iceNodeStyles.xml,
    myLinkStylesFile = http://localhost:55555/xml/iceLinkStyles.xml,
    myActionsFile = http://localhost:55555/xml/iceActions.xml" />

 

 

<param name="initParams" value="
                myTheme = http://localhost:55555/IconLibrary.dll,
                myFirstNode = http://localhost:55555/ICEIdeas.aspx,
                myModeFile = http://localhost:55555/xml/iceSettings.xml,
                myConstantsFile = http://localhost:55555/xml/iceConstants.xml,
                myNodeStylesFile = http://localhost:55555/xml/iceNodeStyles.xml,
                myLinkStylesFile = http://localhost:55555/xml/iceLinkStyles.xml,
                myActionsFile = http://localhost:55555/xml/iceActions.xml" />

 

 

In the short term, these seems to work.  In the future it would be helpful to at least update the documentation or make sure all assemblies are loaded before any of the other initialization occurs. 

Hopefully this helps, let me know if it doesn't make sense.