Debugging the wrong line in UWP (Universal Windows App) in Visual Studio 2015

I had met a debugging issue which ran into the wrong line such as comments line when debug a referenced .Net project in UWP (Universal Windows App) in Visual Studio 2015.

I search around in google and saw some suggestions that convert the source code to ANSI format but it didn't resolve the issue. It took me few hours to found out the Windows Desktop UWP project referenced to the .Net project which was not from the latest build output path "bin\x86\Debug\". Actually it points to path "\bin\ARM\Debug" because it needed debug in "ARM" platform when deploying the Windows phone project to windows phone . I was debugging the wrong project before!!!!
   
After I refer to the correct project reference, I was able to debug code as normal as usual. :)

Comments

Post a Comment

Popular posts from this blog

Top JavaScript courses helping you develop SPFx webPart with ReactJS and AngularJS

Image
As SharePoint 2016 is launched and the SharePoint Framework was announced on 4th of May,  for a SharePoint developer, these are the technologies that you should learn in the next months in order to be prepared to the new framework. They are AngularJS, ReactJS, Node.js and TypeScript. I shared those best online courses from "Udemy.com" in here. Learn anytime, anywhere, on most devices. Each course comes with a 30-day money-back guarantee. Course : Sharepoint: SPFx Development Model - It's providing clear instructions on this new SPFx framework. It delivers an example of full development workflow using Knockout.js JavaScript framework and PnP helper code. Instructor: OLEG RUMIANCEV is a full-time SharePoint ninja currently living in Biddulph, United Kingdom. His interests range from Microsoft and SharePoint to AI, and inspirational TED talks. ReactJS - React is straight JavaScript and more smaller compare with Angular JS. It's emerging in an ecosystem of...
Read more

Effective LLM Prompting skills

Apply best practices for crafting effective prompts to LLM are key for effective prompting to LLM . Here are the best practices. Role assignment: specifying a role for the LLM lead to a more helpful response. You can even a pply multiple roles to LLM Specificity and context: by providing context about your role and the situation and highlighting your specific concerns, you're guiding the LLM to provide specific and relevant information. Feedback to LLM:  You can effectively analyze your prompt based on the LLM response, and identify weaknesses, and points out the targeted improvements for better prompt. For example, you are a software developer and want LLM to review and debug the code errors. Your prompt can be: You are a senior Python developer and tester, I'm a junior Python developer working on a program to calculate daily interest rates. I'm encountering an error when running my code. Could you help me debug it? Here's a snippet of the code: "..."', a...
Read more

Enable the Microsoft Power BI report file type (.pbix) in SharePoint Search

Image
By default, the Microsoft Power BI report file (.pbix) is not in the list of file type in SharePoint 2013 search configuration in Central Admin, and so you wouldn't open the Power BI file directly by clicking the link from the search result page. However, it's easy to add this file type by following configuration. Open “Central Admin” site, and then go to "Manage service applications”->”Search Service Application XX” (use the actual name of the “Search Service Application” in your site). Click on the “File Type” in left side navigation. Click the New File Type button and type PBIX (no period needed) in the File extension box and click OK. Restart the Search Service: Go to local “services”, stop the SharePoint Server Search service and start it again. Reset Your Index: Back on the Search Administration page within Central Administration you will want to click on the Index Reset link under Crawling on the left side menu. Press the Reset Now button. Rem...
Read more