|
Because I need it to be removed, that is why. Hiding is not an option.
|
|
|
|
|
Simply make sure the item is removed. Can you please post the code here (for removing the item).
In general, the remove method works.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
I simply use newAccordion.Items.Remove method. Maybe silverlight is still keeping somewhere the name of this item inside accordion? I made a test and there is no problem with creating i.e. a TextBlock with the same name.
|
|
|
|
|
It seems now that the real problem is the textbox (child of accordion item) that also has the name generated according to accordion.Items.Count. And apparently, when I delete the accordion item this textbox is still somewhere in memory.
Now I don't have time to figure out the proper solution, so I decided to add guid to the name of the textbox and get the accordion.Items.Count value from the name with substring function.
But if anyone could ever find out, how to avoid such problem, please write.
|
|
|
|
|
So I'm coming to the end of phase one and want to set the app up properly. After twattering around with images and the structure of the folders I realised I need to rename 2 of the projects in the application to Admin, the WCF will service both the admin and the public facing site.
I did this with some trepidation (having taken a backup of course)
I now have the following projects
App.WCF
AppAdmin
AppAdmin.Web
My problem is that AppAdmin.web is generating 2 xap files App.xap and AppAdmin.xap and I cannot find out where the old xap file is generated from. This has effectively got rid of the debugging in the AppAdmin project.
Where is the xap generated from.
I also lost the reference to the Assets folder and the styles for some reason. Moving the Styles.xaml to another folder fixed that - weird!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Lesson 1 - get your project names right BEFORE you start coding.
I recreated the entire application using the backup files and all works perfectly (within reason anyway).
Now to work out the security between silverlight and the wcf and we are ready for deploy.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Lesson 1 - get your project names right BEFORE you start coding
That really really holds true for Silverlight. I had a whale of a time changing the xap name once I was midway into the project.
Finally went back and created a new one.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
Deleting all files in the web projects Client Bin and then changing the settings in Properties, Silverlight Applications tab can fix this.
Hope that helps in the future.
|
|
|
|
|
I did all the steps above - not necessarily in that order and repeated numerous times, I still got the 2 xap files and could not reference the Assets folder. I took me about 2 hours to rebuild/structure the app with different project and namespaces, which was less time than I had spent faffing about trying to fix it internally.
I REALLY hope there is not a next time!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Just curious, When you changed the Silverlight project name, did the Xap file name property in the Silverlight Properties tab also change? If not, could that have been the problem?
|
|
|
|
|
Robert Croll wrote: did the Xap file name property in the Silverlight Properties tab also change
I'm not sure, I probably changed it manually and as I did a solution wide search and replace it was certainly changed at some point. What annoyed me was that AFAIK there was no instance of the original project name anywhere in the solution and still it created the original xap field.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hi,
This morning I thought I'll 'quickly' do a POC on a nice thought. The thought involved creating a UserControl, adding a DependencyProperty to the control, setting the value of the property by binding it to a property I have on a class (in XAML declaration), the instance of the class coming from an ObservableCollection and the control is the ItemTemplate in a ListBox, very simple...
until the DependencyProperty never got set by the binding...
I have gone through more than 20 supposed solutions, not 1 of them working when I implement it... If I bind a static resource to the property it works...
Can someone please build me a simple Silverlight project that achieves the above so that I can use it to regain my sanity... Please do not paste code snippets in this response, please send me the zip of the project, I've gone through too many snippets today (I suspect that my sanity stayed behind in one of the snippets  ) (If I can be pickey, SL4 in VS2010 please)
____________________________________________________________
Be brave little warrior, be VERY brave
|
|
|
|
|
Anyone??? PLEASE HELP!
____________________________________________________________
Be brave little warrior, be VERY brave
|
|
|
|
|
I am playing with MVVM.
I'd like to have :
Views in their own project - so I can hive off the project to designers
ViewModels in their own project - which should essentialy serve as teh developers version of the Gui (i.e. the developers don't need to know what it looks like, just make sure the data is provided and updated and functions provided)
Models in their own project - because it seems sensible to me.
Now in addition to all this, it would seem logical to me to have a Controller.
By this I mean a singleton class that 'controls' the application - it provides views and viewmodels, links them together and provides functionality for the viewmodels (e.g. using services to get data, store data, and acting as a 'communicator' between viewmodels (by messaging or events or whatever)
Now it's late and I am tired (and fairly thick), so I am probably missing something really obvious, but where can I stick my controller class?
The View project needs a reference to the ViewModel project (for binding)
The Controller needs a reference to both the ViewModel and View projects (as the controller will instantiate them both)
The controller needs a reference to the model project (so it can make the model data available to the ViewModels)
But (and here's the crux of my problem) the ViewModel needs a reference to the Controller (so it can achieve functionality)
How can I get this to happen without circular references?
I could obviously have the view, ViewModel and Controller all in the same project - but really would prefer not to.
I could do without the Controller and have my ViewModels handle all that stuff directly - but I want to treat my ViewModels as, well, View Models.
Thanks in advance for any advice.
___________________________________________
.\\axxx
(That's an 'M')
|
|
|
|
|
Have just once controller class that knows about all view models. Every view model can access this controller via an interface to the controller. Your circular reference is gone (well somewhat gone).
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
My latest tip/trick
Visit the Hindi forum here.
|
|
|
|
|
Yes - I think an interface is the way to go. I was intending on a single controller instance that knows about all view models (it will be instantiating them).
But the View model needs an instance of the Controller - so I guess I will have to set the IController property of the ViewModel when the Controller instantiates it.
Thanks
___________________________________________
.\\axxx
(That's an 'M')
|
|
|
|
|
May I recommend that, instead of this approach, you take a look at the work that Marlon Grech did on MefedMVVM[^]. This simplifies the whole architecture quite significantly, and will give your designers that warm gooey feeling.
|
|
|
|
|
Pete O'Hanlon wrote: May I recommend that
Yes indeed, of course you may.
I just really didn't want to use a framewrk - because I find that I learn by doing - so by developing my own methodology, making mistakes, and fixing them, I understand the underlying issues. Then I can use a framework.
But Maron's stuf does look interesting -so looks like it's yet another framework I'll have to download and play with!
Thanks
___________________________________________
.\\axxx
(That's an 'M')
|
|
|
|
|
If you need help, just ask - I helped Marlon develop it.
|
|
|
|
|
Hi,
I want to draw too many shapes in canvas (Rectangles, ellipses, etc.). For that, i need the drawingContext.
How can i create and attach the drawingContext in Canvas control.
Is there any other simple way to do so?
|
|
|
|
|
To get the drawing context, you can simply override the OnRender on a derived canvas object.
|
|
|
|
|
hi..... to all....
i'm new to silverlight ...
my doubt is.... for ssrs reports there's an BIDS( bussiness intellegent development studio) ..
now i want to design reports in silverlight reporting services is there any development studio for
silverlight reporting services.... if yes please give me the download site... i want to download...
please help me....
|
|
|
|
|
Reporting services reportviewer is not supported in silverlight - you need to call an ASP page for the viewer.
RS development is not done in Silverlight, there is no BIDS done in SL.
There is a 3rd party SL reportviewer but it costs $500.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
ok.... but how can i design silverlight reports.. in silverlight application..
i've worked on crystal reports , ssrs, and now silverlight reports..
but i cant get were to design the silverlight reports...
|
|
|
|
|
I used this article [^]as the basis for my solution.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
