Advanced Forum Search Results
-
Did you find any direction on the pdb getting packaged up in the xap?
-
I have a project that requires me to compile without Visual Studio or MSBuild. I have to go straight through csc, however whenever I run it on the project that hasn't been built by V.S. first I get compiler errors saying it can't access items that would have been created pre-compile time by VS in the *.g.cs files...
I've read that ...
-
when a Debug.Assert fails it pops up a Modal message box that halts any unit tests from continuing until you click ok/cancel.
I found this post about how to override the default behavior.
http://msmvps.com/blogs/paulomorgado/archive/2008/12/03/improving-debugging-and-testing-through-assertions.aspx
except we don't have ...
-
Thanks to Oleg,
You can read about how to make T4 templating work within Silverlight at my blog...
http://staxmanade.blogspot.com/2008/12/t4-text-templating-in-silverlight.html
-
Thanks for the suggestion... I thought about that one, and may still be an option.
I sent an email to the Oleg Sych. I'll let you know if helps me figure something out.
-
I tried creating a new Silverlight project, removing all the references that I could possibliy remove without loosing the ability to compile the silverlight application.
Then adding a file called TextFile1.tt -> which created a TextFile1.cs automatically under it. and I'm getting three errors...
Error 1 Compiling transformation: ...
-
Thanks Justin,
Actually we put this logic back in the business model object to enforce the business rule.
However, your method could work as well...
-
When I set the NumericUpDown.DecimalPlaces to zero and enter a value of 10.5, the display shows 11, but the actual Value of the control is still 10.5.
What's the story where a user can't see the decimal places, but can enter special values?
If this must be supported, can we have an option to force the Value to what the user ...
-
Is this more related to Serialization in general? When an object is deserialized from (in this case) xml/soap the deserializer is by-passing the object's constructor...
What I was trying to do was get the object to hook up to it's own PropertyChanged event w/out having to specifically call some "Initialize" method by it's ...
-
So there's no other way besides writing our own hackish/plumming to get classes to instanciate the way we expect classes in .net to be constructed?
Is this an item on Silverlight's TODO list? or is there some special security reason for this?