App certification issue : Debug configuration test

Question

  My app fails to pass certification due to following reason:

Debug configuration test

FAILED

Debug configuration

• Error Found: The debug configuration test detected the following errors:
• The binary NotificationsExtensions.winmd is built in debug mode.

What does this mean and how to remove that debug mode?

  I've tried to remove and add NotificationsExtensions.winmd file from App Tiles and badges sample number of time. I tried to build this sample again and again, but I get only "debug" folder and not a "Release" folder.

I'm trying to get my app into "Release" mode through project properties and also from ACK. But these error is still there, same. What am I missing?

Answer 1

When you build the components and your application make sure you set the configuration manager to build Release Mode.  Then ensure your app passes the WACK tests before you send your app up for certification.

---

Jeff Sanders (MSFT)

@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)

Answer 2

"When you build the components and your application make sure you set the configuration manager to build Release Mode"

  Once again I tried this option. From Visual Studio,  I choose "Debug --> myProject Propertis --> configuration Manager - Release Mode.

  Then I choose Store --> create app package -- I chose "NO" to upload package to the store. -- So I get WACK on my machine.

 Still the WACK fails for same reason: 

• The binary NotificationsExtensions.winmd is built in debug mode.

 I also tried to select project from Solution Explorer, right click it and then make it in "release mode".. No success yet...

Answer 3

We will need some more information.  Where are you getting NotificationsExtensions from?  What version of WACK and Visual Studio are you running?  Can you reproduce the problem with a new blank application or just this one?

---

Jeff Sanders (MSFT)

@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)

Answer 4

I'm using Visual Studio Express 2012 for Windows 8 and WACK 2.2.

NotificationExtensions are local.

Answer 5

  The problem is solved. First I removed notificationsExtensions reference and file from my project.

  I closed everything out and restarted my machine and took a break.

  I relaunched App tiles and badged sample in Visual Studio and clean the solution. Then build it. This time I got that "Release" folder inside this projects folders. I copied that notification.winmd binary file into my app project and added reference to it. Then build my project again. And this time, the WACK PASSED.!!!

---

sonal