Ok fixed the problem. The references to System.Web.Extensions were pointing
to an old version. I think the new version is the 3.5 version. I did a
compare and copied over all the references to that dll and it's working now.
*whew*
Always the way, 10 minutes after you post for help you find the answer
yourself (after hours of banging head against wall). Hope this helps someone
down the track. :)
cheers,
Stephen
On Thu, Sep 18, 2008 at 5:19 PM, Stephen Price <[EMAIL PROTECTED]>wrote:
> I've been working on a Silverlight app hosted in a DotNetNuke module
> (thanks for the post Philip!) and have hit a weird problem when I uploaded
> the module to the test server.
> A critical error has occurred.
> The control with ID 'SilverlightModule' requires a ScriptManager on the
> page. The ScriptManager must appear before any controls that need it.
>
>
> Any ideas? I've been trying to figure out what the differences are between
> my machine and the server. I've got three DNN installations on my machine
> and it works flawlessly locally. For some reason the server is not
> registering the Scriptmanager.
> I've checked the source of the page on my machine and can see the script
> that registers the scriptmanager but its missing from the server's source.
> (source being viewed via browser)
>
> <script src=
> "/Dnn_Auth/ScriptResource.axd?d=svo06Iew2oldx8fZ_h3P_-Kra0ZdVOBxf3F5WVkyvImxAtOfVoxE3zO-vCOG4gpJ_jQOg2GPuFI1&t=32af477a"
> type="text/javascript"></script><script type="text/javascript">
> //<![CDATA[
> Sys.WebForms.PageRequestManager._initialize('ScriptManager',
> document.getElementById('Form'));
> Sys.WebForms.PageRequestManager.getInstance()._updateControls([], [], [],
> 90);
> //]]>
> </script>
>
> This is the code I'm using to register the scriptmanager;
>
> if (!DotNetNuke.Framework.AJAX.IsEnabled()) {
> DotNetNuke.Framework.AJAX.RegisterScriptManager();
> }
> (started off without the check to see if IsEnabled is not true)
> help! stuck!
>
> thanks,
> Stephen
>
> On Mon, Sep 8, 2008 at 9:34 PM, Philip Beadle <[EMAIL PROTECTED]>wrote:
>
>> Here's the first post on DNN + SL
>>
>>
>>
>> http://philipbeadle.net/Default.aspx?tabid=53&EntryID=110
>>
>>
>>
>>
>>
>> Regards,
>>
>> *Philip Beadle*
>> Readify | Principal Consultant
>> Microsoft MVP - ASP/ASP.NET, MCAD, MCT
>>
>> Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia
>> M: +61 417 301 024 | E: [EMAIL PROTECTED] | C:
>> [EMAIL PROTECTED] | W: www.readify.net
>>
>>
>>
>> *From:* [EMAIL PROTECTED] [mailto:
>> [EMAIL PROTECTED] *On Behalf Of *Stephen Price
>> *Sent:* Monday, September 01, 2008 5:17 PM
>>
>> *To:* [email protected]
>> *Subject:* Re: [OzSilverlight] Accessing the App.xaml resources
>>
>>
>>
>> Awesome, make sure you blog that Silverlight/DNN stuff, I'm looking at
>> getting that happening myself.
>>
>>
>>
>>
>>
>> On Mon, Sep 1, 2008 at 1:47 PM, Philip Beadle <[EMAIL PROTECTED]>
>> wrote:
>>
>> That worked nicely. I forgot the INotifyPropertyChanged and went off on a
>> tangent when it didn't work J
>>
>>
>>
>> Make sure you come and give us a hand in the Dev Garten. We are building
>> a DotNetNuke site with a bunch of Silverlight modules J
>>
>>
>>
>> Regards,
>>
>> *Philip Beadle*
>> Readify | Principal Consultant
>> Microsoft MVP - ASP/ASP.NET <http://asp.net/>, MCAD, MCT
>>
>> Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia
>> M: +61 417 301 024 | E: [EMAIL PROTECTED] | C:
>> [EMAIL PROTECTED] | W: www.readify.net
>>
>>
>>
>> *From:* [EMAIL PROTECTED] [mailto:
>> [EMAIL PROTECTED] *On Behalf Of *Jonas Follesø
>>
>>
>> *Sent:* Monday, September 01, 2008 3:24 PM
>> *To:* [email protected]
>> *Subject:* Re: [OzSilverlight] Accessing the App.xaml resources
>>
>>
>>
>> Hi,
>>
>>
>>
>> Silverlight does not support binding against static classes. One thing you
>> could do is something like this:
>>
>> Create a simple binding helper class that implements
>> INotifyPropertyChanged, and with one Bool property.
>>
>> Then create a app level resource like this:
>>
>> <Application.Resources>
>> </myapp:BindingHelper x:Key="bindingHelper" />
>> </Application.Resources>
>>
>> Then in your App_Startup, you can fetch out your InitParam set through
>> HTML when initializing your app. Then do this in App_Startup:
>>
>> ((BindingHelper)Resources["bindingHelper"]).IsVisible =
>> Convert.ToBoolean(e.InitParam["myInitParam"]);
>>
>> Then where ever you need to hide/show stuff in your app you can use
>> standard binding.
>>
>> <Button Enabled="{Binding Path=IsVisible, Path={StaticResource
>> bindingHelper}}" />
>>
>> See you in Sydney!
>>
>> Cheers,
>> Jonas
>>
>> On Mon, Sep 1, 2008 at 5:06 PM, Philip Beadle <[EMAIL PROTECTED]>
>> wrote:
>>
>> Hi All,
>>
>>
>>
>> What i want to do is bind to a list of items and have a button that is
>> either visible or not depending on an InitParam. Whats the best way to do
>> this?
>>
>> I have tried to make a static resource in App.xaml but i cant access it to
>> change the value. I have a static variable in App.xaml.cs but can't figure
>> out how to write that into the xaml.
>>
>>
>>
>> Cheers
>>
>>
>>
>> Regards,
>>
>> *Philip Beadle*
>> Readify | Principal Consultant
>> Microsoft MVP - ASP/ASP.NET <http://asp.net/>, MCAD, MCT
>>
>> *Error! Filename not specified.*
>>
>> Suite 206 Nolan Tower | 29 Rakaia Way | Docklands | VIC 3008 | Australia
>> M: +61 417 301 024 | E: [EMAIL PROTECTED] | C:
>> [EMAIL PROTECTED] | W: www.readify.net
>> ------------------------------
>>
>> The content of this e-mail, including any attachments is a confidential
>> communication between Readify Pty Ltd and the intended addressee and is for
>> the sole use of that intended addressee. If you are not the intended
>> addressee, any use, interference with, disclosure or copying of this
>> material is unauthorized and prohibited. If you have received this e-mail in
>> error please contact the sender immediately and then delete the message and
>> any attachment(s).
>>
>> *P** **Please consider your environmental responsibility before printing
>> this e-mail*
>>
>>
>>
>> -------------------------------------------------------------------
>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>> the list with 'unsubscribe' as the subject.
>> Powered by mailenable.com - List managed by www.readify.net
>>
>>
>>
>> -------------------------------------------------------------------
>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>> the list with 'unsubscribe' as the subject.
>> Powered by mailenable.com - List managed by www.readify.net
>>
>> -------------------------------------------------------------------
>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>> the list with 'unsubscribe' as the subject.
>> Powered by mailenable.com - List managed by www.readify.net
>>
>>
>>
>> -------------------------------------------------------------------
>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>> the list with 'unsubscribe' as the subject.
>> Powered by mailenable.com - List managed by www.readify.net
>> -------------------------------------------------------------------
>> OzSilverlight.com - to unsubscribe from this list, send a message back to
>> the list with 'unsubscribe' as the subject.
>> Powered by mailenable.com - List managed by www.readify.net
>>
>
>
-------------------------------------------------------------------
OzSilverlight.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net
