Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

windows phone 7 - Caliburn.Micro(.WP7) and Bing Maps Crashing -


i have app i'm upgrading beta bits - , map screen crashing. try bottom of - started brand new - blank "win phone application".

referenced caliburn.micro (just built new code last night) version: caliburnmicro_1296ea635677 (from codeplex)

referenced microsoft.phone.controls.map.dll

and in mainpage added

<grid>  <maps:map /> </grid> 

and add bootstrapper app.xaml

<wp7:phonebootstrapper x:name="bootstrapper" /> 

when page runs in phone emulator - main page renders , see map of world. if click anywhere on page - unhandled exception of "the parameter incorrect"

if remove

from app.xaml - map works correctly.

what think?

thanks advice?

i have found answer.

the key here - had setup , wroking beta templates - , stopped working when moved winphone rtm templates in vs2010.

caliburn work on behalf, "added" rtm templates - conflicting each other. in end problem has/had nothing bing maps control - happens - first screen - that's trying solve problem.

this ever not-helpful exception:

the parameter incorrect 

which, i'm pretty sure happen on screen - if went upgrade path of templates, did. here had remove - normal. in new app.xaml.cs - removed (by commenting) in app ctor ...

// phone-specific initialization // initializephoneapplication();   // global handler uncaught exceptions.  // unhandledexception += application_unhandledexception; 

and removed these method bodies, because it's dead code after removing initializephoneapplication() call ctor ...

// code execute when application launching (eg, start) // code not execute when application reactivated private void application_launching(object sender, launchingeventargs e) { }  // code execute when application activated (brought foreground) // code not execute when application first launched private void application_activated(object sender, activatedeventargs e) { }  // code execute when application deactivated (sent background) // code not execute when application closing private void application_deactivated(object sender, deactivatedeventargs e) { }  // code execute when application closing (eg, user hit back) // code not execute when application deactivated private void application_closing(object sender, closingeventargs e) { }  // code execute if navigation fails private void rootframe_navigationfailed(object sender, navigationfailedeventargs e) {     if (system.diagnostics.debugger.isattached)     {         // navigation has failed; break debugger         system.diagnostics.debugger.break();     } }  // code execute on unhandled exceptions private void application_unhandledexception(object sender, applicationunhandledexceptioneventargs e) {     if (system.diagnostics.debugger.isattached)     {         // unhandled exception has occurred; break debugger         system.diagnostics.debugger.break();     } }  #region phone application initialization  // avoid double-initialization private bool phoneapplicationinitialized = false;  // not add additional code method private void initializephoneapplication() {     if (phoneapplicationinitialized)         return;      // create frame don't set rootvisual yet; allows splash     // screen remain active until application ready render.     rootframe = new phoneapplicationframe();     rootframe.navigated += completeinitializephoneapplication;      // handle navigation failures     rootframe.navigationfailed += rootframe_navigationfailed;      // ensure don't initialize again     phoneapplicationinitialized = true; }  // not add additional code method private void completeinitializephoneapplication(object sender, navigationeventargs e) {     // set root visual allow application render     if (rootvisual != rootframe)         rootvisual = rootframe;      // remove handler since no longer needed     rootframe.navigated -= completeinitializephoneapplication; }  #endregion 

special rob solving mystery!


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -