Portal Engine Questions on portal engine and web parts.
Version 6.x > Portal Engine > Problem debugging webpart in Visual Studio View modes: 
User avatar
Member
Member
stephen.turley-terradon - 11/15/2012 11:31:20 AM
   
Problem debugging webpart in Visual Studio
I recently made some changes to a custom webparts source code. Now when I try to set a break point to inspect it at run-time, I get the following message:
the breakpoint will not be hit no symbols loaded for this document

I've tried rebuilding the entire site and have ensured that debug is set to true in my web.config.

Anyone have a suggestion of what to try?

User avatar
Member
Member
stephen.turley-terradon - 11/16/2012 11:57:58 AM
   
RE:Problem debugging webpart in Visual Studio
This is now happening on other Kentico sites I'm debugging. Any ideas?

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 11/24/2012 3:01:42 AM
   
RE:Problem debugging webpart in Visual Studio
Hi Stephen,

Could you please tell me which .NET version are you using?

Best regards,
Martin Danko

User avatar
Member
Member
stephen.turley-terradon - 11/26/2012 11:53:53 AM
   
RE:Problem debugging webpart in Visual Studio
.NET 4.0 Visual Studio 2010

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 11/28/2012 10:35:24 AM
   
RE:Problem debugging webpart in Visual Studio
Hi Stephen,

Could you please try to delete all temporary ASP.NET files. This is how you do it:

Locate your temporary ASP.NET files and delete them. They're probably located in
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
and
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
Then rebuild your project and you should be fine - the breakpoint should be hit.

Best regards,
Martin Danko

User avatar
Member
Member
stephen.turley-terradon - 12/3/2012 1:10:08 PM
   
RE:Problem debugging webpart in Visual Studio
I followed the steps that you outlined and it is still doing the same thing.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 12/9/2012 2:47:45 AM
   
RE:Problem debugging webpart in Visual Studio
Hi,

Is the break point hit when you navigate to a page which contains that web part with the break point?

Best regards,
Juraj Ondrus

User avatar
Member
Member
stephen.turley-terradon - 12/10/2012 9:25:22 AM
   
RE:Problem debugging webpart in Visual Studio
No. It seems like this problem started after installing the MVC framework for another project.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 12/12/2012 1:51:14 AM
   
RE:Problem debugging webpart in Visual Studio
Hi,

What was the installation process? Have you tried re-installing the Visual studio?
Do you have the same issue also for non-Kentico projects?

Best regards,
Juraj Ondrus

User avatar
Member
Member
stephen.turley-terradon - 12/12/2012 7:53:55 AM
   
RE:Problem debugging webpart in Visual Studio
I just checked it on a non-Kentico site and it works fine.

I installed the Kentico site by using the web installer, patching the site, and importing the site and assemblies. I also had to copy some custom code over manually.

I installed a copy of Visual Studio 2012 and it had the same behavior.

User avatar
Member
Member
stephen.turley-terradon - 12/12/2012 9:08:49 AM
   
RE:Problem debugging webpart in Visual Studio
I've noticed that there is similar behavior on remote sites.

If I change the source file for a WebPart for example, the new code is not compiled. I have to change the web.config file and force the site to recompile.

In one instance we had a runtime error. I commented the line of code causing the problem out, but the runtime error was still hitting that line of code.

Is this a setting in web.config I need to look at?

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 12/13/2012 1:38:20 AM
   
RE:Problem debugging webpart in Visual Studio
Hi,

I am not aware of any settings and also no other customers are reporting this. It must be something environment related. Are you able to reproduce it on other machines too? Maybe your .Net is not configured well. I would try reinstalling it as well.

Change in web.config file forces the application to be restarted and recompiled.

Also, could you please create a screen cast of your issue so we can see the exact steps? Please click on the "Record a screecast of your issue" button on our support page.

Thank you.

Best regards,
Juraj Ondrus