|
This started happening immediately after I installed the Infragistics toolkits (and without even using them).
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Hi John,
Generally we face this issue when we have a bad XAML. But in your case, did you add the reference of your external library in your project? If that is the case, then it might be because that is trying to access the same library from both the assembly.
Can you please try uninstalling the external library and reinstalling it again?
|
|
|
|
|
The Infrashitstix charts don't crash the app. I have no idea why they're interfering with the standrad charts unless its object name collisions of some sort.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
hi John i am facing the same issue and my xaml is fine, did you find the problem ?
Vuyiswa Maseko,
Spoted in Daniweb-- Sorry to rant. I hate websites. They are just wierd. They don't behave like normal code.
C#/VB.NET/ASP.NET/SQL7/2000/2005/2008
http://www.vuyiswamaseko.com
vuyiswa@its.co.za
http://www.itsabacus.co.za/itsabacus/
|
|
|
|
|
I have a path being drawn (in the shape of a triangle). I need the triangle to be the static height, but the width needs to change to fit inside its container element. How do I go about doing that? The container in question is a variable number of Border components placed in a grid (and a grid-column).
SOLUTION: Used a RenderTransform.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Awesome 
Regards - Kunal Chowdhury | Software Developer | Chennai | India | My Blog | My Tweets
|
|
|
|
|
I could use some recommendations for an entry level WPF book.
Thanks
Everything makes sense in someone's mind
|
|
|
|
|
Hy,
there are some nice articles here on CP especially by Josh Smith and the Barber(Sacha)
As for books I would recommend three:
1) Teach yourself WPF in 24 Hours by Sams(really good for beginers)
2) WPF Unleashed - also by Sams => really good book. If you're not a total begginer you could skip the first one.
3) And finally WPF Control Development Unleashed (Building advanced UX(user experiences)).
The third book should only be aproached once you have the basics figured out.
|
|
|
|
|
|
I've had this problem for years on XP and Server 2003 (newer OS's don't seem to have a problem). Whenever the resolution changes it gets into this state. The patch didn't do anything for me - I either have to restart or use the arrow keys to move through the combo box items. This could be fixed in 4.0, I have not tried. I'm still on 3.5 SP1.
|
|
|
|
|
I am on 3.5 as well. I am in a process to create a prototype and propose WPF for our new application suite. Now this bug scales down all the UI I have done so far using Transparency and rounded window etc.
Yes, this problem is specific to XP and I don't think we are upgrading to Win7 anytime soon at our enterprise level.
A naive question, ideally, to develop using .NET 4.0 would I need to upgrade to VS 2010?
|
|
|
|
|
It's not a naive question. Given the fact that VS allows multi-targetting, this is a perfectly reasonable question. The answer, is yes - you really do need to upgrade to VS2010.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Thanks Pete.
Upgrading it to VS2010 is another issue for us at the moment, VS2008 would be OK. I think I am going to have a bit hard time presenting WPF as the better candidate for our Enterprise apps. An alternate option being considered is Google Web Toolkit/Java at the moment.
We have quite a few native apps in VS2003 and .NET apps in 2005. I recently started using VS2008 for WPF.
I tried installing .NET 4 and it failed on XP! I found quite a few people have this issue. I'll dig into this sometime later today.
|
|
|
|
|
Hi all,
I'm excited to inform you that CodeFort with its release last week broke the barrier and became the first .NET obfuscator to support renaming of identifiers in XAML and BAML code. This is a huge step forward in .NET obfuscation technology, because it removes the need to manually exclude all the Presentation Layer properties and types from obfuscation, as you need to with most obfuscation tools today. Of course it will mean a great improvement in security in terms of protecting your intellectual property rights from attackers.
CodeFort also comes with a range of powerful protection features such as Reference Scrambling and Anti-Tampering, making it a state-of-the-art protection tool. Reference Scrambling decouples the link between calls to external methods, and the reference to those methods, making it impossible for an attacker to browse through IL or disassembled code, because the method calls are pointing to unusable locations.
Check out the free version if you're interested - we are very much looking forward to your feedback!
CodeFort Free Edition [codefort.org]
Best regards,
Christian
email: support (.) creatix.dk
|
|
|
|
|
We certainly agree that applying renaming to XAML/BAML resources has been a longstanding limitation for obfuscators. We have also been working on this problem and we too are in the final phase of beta testing the latest Dotfuscator release. In this latest release, Dotfuscator is extending renaming into your XAML/BAML. This has three benefits; more of your assembly is protected, your XAML/BAML is protected, and you save time since configuration is now much simpler.
If you would like to run your application through this beta version of Dotfuscator, just email me (sebastian@preemptive.com) and I will have our support team send you credentials. This is beta – there are no fees – and you will have access to our support – but you cannot use this version for any production work. .NET 1.1 or higher is the only requirement.
We are seeing good results - for example, three production applications yielded the following increased coverage:
• Medical imaging – increased protected surface from 27% to 100%.
• Measuring device – increased protected surface from 26% to 78%.
• Software development tool – increased protected surface from 61% to 100%.
…but we want to be sure we are covering all bases – so challenge us with your most complex WPF applications and let’s see how we do. Thanks!
|
|
|
|
|
When I run my Silverlight application, there was a message in Output Window: "The thread '<No Name>' (0xd88) has exited with code 0 (0x0)." Then, my application cannot run, and Why?
|
|
|
|
|
Goto Debug options on the Visual Studio menu, choose exceptions, and check all items.
Run your code again and see if an error is now thrown by the code.
|
|
|
|
|
If you run any .NET application you will see this message at the end of execution.
It is a standard message indicating that the thread ended, that there was no exception, and that the return code was 0.
So you need to look at anywhere in your code where you are ending the thread or attempting to execute and instance of an object but not keeping a reference to that object.
Try putting a breakpoint in the first line of your application and see what happens when you walk through the code. If your code debugging just 'disappears' with the application ending, then the problem is the way the Sharepoint app is being loaded at the higher level.
|
|
|
|
|
Hi forPower,
You can check your Application_Startup event inside your App.xaml file whether you are setting your RootVisual or not. If you are not setting anything to RootVisual it might exit.
Have a look into this: App.xaml File Structure[^]
Also check whether you are exiting the application by mistake.
|
|
|
|
|
Hi
In Excel, there is this feature for filtering the cells of a column.
How can I implement excel like FILTER feature in Silverlight Datagrid?
Please advice. Thanks
AJ
Follow your goals, Means will follow you ---Gandhi---
|
|
|
|
|
There are plenty of different approaches available.
Do a search on the internet to comapare these approaches - some may be better for SL2 and others for SL3 and SL4.
Have a look here to see an implementation of the PagedCollectionView.
|
|
|
|
|
|
Hi its been a while since I've had a problem, but this has stumped me.
I have a start-up screen which has three button on it and one of these opens another WPF window. I would like the window that opens to be able to be closed and re-opened if the button on the start screen is pressed again. However it seems to be crashing and the error I get is:
Cannot convert the value in attribute 'Content' to object of type 'System.Object'. Specified element is already the logical child of another element. Disconnect it first. Error at object 'System.Windows.Controls.ContentControl' in markup file 'VisualEditor;component/designer.xaml' Line 28 Position 46.
Any help is much appreciated.
Gretna
Some people are like slinky's... They're not really good for anything but they bring a smile to your face when pushed down the stairs
|
|
|
|
|
Hy,
Since you haven't shown any code or Xaml that you have, based on the error message, I would say/guess
that your designer.xaml markup holds a reference to the sencond window(or a CONTROL in it) that you are trying to open/close.
this really silly code inside window1/mainwindow works just fine:
private Window2 w2 =null;
private void button1_Click(object sender, RoutedEventArgs e)
{
if (w2 == null)
{
w2 = new Window2();
w2.Show();
}
else
{
w2.Close();
w2 = null;
}
e.Handled=true;
}
|
|
|
|
|
Cheers for your reply.
It didn't seem to work still but I have had an epiphany and manage to solve it thanks again for the help. It was because the content of some of my items on my second form was using static resource so on close of the second window I set the content to null.
Gretna.
Some people are like slinky's... They're not really good for anything but they bring a smile to your face when pushed down the stairs
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
