Very strange behavior - recompiling EXE when XAML saved

I’m running into something in Oxygene that is really damn peculiar. When I make a change to my XAML and click save, I see the timestamp on the EXE update as if it recompiled or in some way changed it. If I then run that EXE, it always throws an error and dies. But then if I do a force rebuild of the app (without making any more changes), the EXE produced is fine again. And when I say I change the XAML, this can be as trivial as adding a space then deleting it and hitting save (so no functional change).

Here’s the error:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: overweb.exe
Problem Signature 02: 1.0.0.1
Problem Signature 03: 5419a6d7
Problem Signature 04: PresentationFramework
Problem Signature 05: 4.0.30319.18408
Problem Signature 06: 52312f13
Problem Signature 07: a19
Problem Signature 08: 46
Problem Signature 09: System.IO.IOException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Oh, versions:
Elements 7.1.75.1557
Visual Studio 2012 Shell (Integrated) 11.0.61030.0 Q11REL
Windows 7 32 bit

Thanks, logged as bugs://69691: Very strange behavior - recompiling EXE when XAML saved

That’d probably designed? VS needs to rebuild the project to know about the types in the XAML for CC & co.

But surely the invalid EXE produced by it is a bug.

Hm yes, i missed that part. that sounds like a bug, yes.

bugs://69691 got closed as fixed

Hello,
I still have cases where the EXE is invalid:

  1. I compile the application
  2. I run the application: OK.
  3. I close the XAML file that was opened: long wait.
  4. I run the application: it doesn’t run anymore.

Now, some questions about this compilation:

  1. Is it possible to run it in background, so that VS is not frozen while compiling?
  2. If the application is running, the compilation is much more longer (it waits to write the EXE file). Is it possible to avoid this?

Up.
Please reopen the bug.

Up
!!! Please reopen !!!

My application is working fine.
I close the opened source files and the application no more works.
If I generate an install without recompiling the application, my clients cannot run the application.
It’s a big problem.

bugs://69691 got reopened.

Sorry for the delay.

bugs://69691 got closed with status fixed.

Corrected in .1705, thanks.

1 Like

bugs://69691 got reopened.

bugs://69691 got closed with status fixed.