StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Can no longer step thru framework code

Can no longer step thru framework code

Marcia G Akins — Mon, 05 Oct 2009 13:47:06 GMT

When I try to step through this line:

this.FillDataTable(loCommand);

shouldn't the debugger dtep into the framework code? Well, it doesn't ever since I upgraded. Is there something that I need to do to make this work again?

TIA

RE: Can no longer step thru framework code

Marcia G Akins — Mon, 05 Oct 2009 13:47:06 GMT

[quote][b]Trent L. Taylor (09/29/2009)[/b][hr]Great! I am glad to hear that you got it working! :)

In regards to the definition of insanity....the sad thing is that it works sometimes in the .NET (or programming in general) world and is why most of us are right on the cusp of a trip to the funny farm (or at least the liquor store)! :D[/quote]

LOL!!! Sad, but true :P

RE: Can no longer step thru framework code

Trent L. Taylor — Tue, 29 Sep 2009 13:54:32 GMT

Great! I am glad to hear that you got it working! :)

In regards to the definition of insanity....the sad thing is that it works sometimes in the .NET (or programming in general) world and is why most of us are right on the cusp of a trip to the funny farm (or at least the liquor store)! :D

RE: Can no longer step thru framework code

Marcia G Akins — Tue, 29 Sep 2009 13:44:19 GMT

[quote][b]Trent L. Taylor (09/29/2009)[/b][hr][quote]
Be sure that you have downloaded the most recent source code. You may even want to backup and remove the source that you have on disk before extracting the newly downloaded source code to make sure that it is overwritten.

Then go through the same process I previously mentioned.[/quote]

Hi Trent. Thanks for sticking with me. I finally got this working. What I did was to delete the source code and start again from scratch. I re-downloaded the source code and the installation, re-ran the install and then rebuilt the source. The definition of insanity is trying the same thing over and over again and expecting a diffeerent result :D

RE: Can no longer step thru framework code

Trent L. Taylor — Tue, 29 Sep 2009 12:59:52 GMT

[quote]OK - I finally figured out that I had to builkd the individual projects before rebuilding the solution [Smile] However, when I rebuild MicroFour StrataFrame UI, it shows up in the gac as version 1.6.0 [/quote]

Be sure that you have downloaded the most recent source code. You may even want to backup and remove the source that you have on disk before extracting the newly downloaded source code to make sure that it is overwritten.

Then go through the same process I previously mentioned.

RE: Can no longer step thru framework code

Trent L. Taylor — Tue, 29 Sep 2009 12:58:35 GMT

That is OK. First, after you delete the SF assemblies, get out of Visual Studio. Next, open the SF source code and rebuild the source code in Debug Mode.

Next, get out of VS again. After this is done, open your project and make sure that your references are pointing to the 1.7.0 assemblies, not the 1.6.0 assemblies.

At this point, you should be on the SF assemblies compiled in debug mode and your project will be referencing the 1.7 assemblies (which these assemblies may have never been updated which could cause all types of "gremlins").

RE: Can no longer step thru framework code

Marcia G Akins — Tue, 29 Sep 2009 12:57:39 GMT

[quote][b]Trent L. Taylor (09/29/2009)[/b][hr]

You got it. When you build a project in debug mode, it produces a pdb file which contains all of the debug information as well as any content information. You will select this from the configuration manager. Generally, I setup my toolbar within VS to have the current build configs as a combo as well as the CPU build type:

[/quote]

OK - I finally figured out that I had to builkd the individual projects before rebuilding the solution :) However, when I rebuild MicroFour StrataFrame UI, it shows up in the gac as version 1.6.0 :(

I also get these errors when I try to build MicroFour StataFrame Extended UI:

Error 1 The type or namespace name 'Application' does not exist in the namespace 'MicroFour.StrataFrame' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataCollapsableContainer.cs 1 29 MicroFour StrataFrame UI Expanded
Error 2 The type or namespace name 'Application' does not exist in the namespace 'MicroFour.StrataFrame' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataListView.cs 1 29 MicroFour StrataFrame UI Expanded
Error 3 The type or namespace name 'StrataUserControlBase' does not exist in the namespace 'MicroFour.StrataFrame.UI.Windows.Forms' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataListView.cs 28 74 MicroFour StrataFrame UI Expanded
Error 4 The type or namespace name 'StrataUserControlBase' does not exist in the namespace 'MicroFour.StrataFrame.UI.Windows.Forms' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataCollapsableContainer.cs 28 86 MicroFour StrataFrame UI Expanded
Warning 5 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 952 21 MicroFour StrataFrame Base
Warning 6 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1058 21 MicroFour StrataFrame Base
Warning 7 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1332 17 MicroFour StrataFrame Base
Warning 8 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1466 17 MicroFour StrataFrame Base
Warning 9 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1666 21 MicroFour StrataFrame Base
Warning 10 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1776 21 MicroFour StrataFrame Base
Warning 11 Could not resolve this reference. Could not locate the assembly "MicroFour StrataFrame Business, Version=1.7.0.0, Culture=neutral, PublicKeyToken=99fe9917f71608a7, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MicroFour StrataFrame UI Expanded
Warning 12 Could not resolve this reference. Could not locate the assembly "MicroFour StrataFrame UI, Version=1.7.0.0, Culture=neutral, PublicKeyToken=99fe9917f71608a7, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MicroFour StrataFrame UI Expanded
Warning 13 The referenced component 'MicroFour StrataFrame Business' could not be found.
Warning 14 The referenced component 'MicroFour StrataFrame UI' could not be found.

RE: Can no longer step thru framework code

Marcia G Akins — Tue, 29 Sep 2009 12:47:41 GMT

[quote][b]Trent L. Taylor (09/29/2009)[/b][hr][quote]I hate to be stupid about this, but I am still a newbie [Smile] Can I just delete the 1.6 assemblies and not do anything else?[/quote]

You are not stupid at all! This is one of those things that once you know you know. But the first time or two may be the learning curve.

Yes. You can delete the SF assemblies from the GAC without any issue.

[quote]To build in debug mode, is all I have to do is handle that in the configuration manager?[/quote]

[/quote]

Well, I deleted the assemblies from the gac and now I can't build. These are the errors:

Error 1 The type or namespace name 'Application' does not exist in the namespace 'MicroFour.StrataFrame' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataCollapsableContainer.cs 1 29 MicroFour StrataFrame UI Expanded
Error 2 The type or namespace name 'Application' does not exist in the namespace 'MicroFour.StrataFrame' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataListView.cs 1 29 MicroFour StrataFrame UI Expanded
Error 3 The type or namespace name 'StrataUserControlBase' does not exist in the namespace 'MicroFour.StrataFrame.UI.Windows.Forms' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataListView.cs 28 74 MicroFour StrataFrame UI Expanded
Error 4 The type or namespace name 'StrataUserControlBase' does not exist in the namespace 'MicroFour.StrataFrame.UI.Windows.Forms' (are you missing an assembly reference?) D:\Strataframe\SourceCode\MicroFour StrataFrame UI Expanded\Controls WinForms\StrataCollapsableContainer.cs 28 86 MicroFour StrataFrame UI Expanded
Warning 5 Unable to delete file "D:\Strataframe\SourceCode\MicroFour StrataFrame Base\obj\Debug\MicroFour StrataFrame Base.pdb". Access to the path 'D:\Strataframe\SourceCode\MicroFour StrataFrame Base\obj\Debug\MicroFour StrataFrame Base.pdb' is denied. MicroFour StrataFrame Base
Warning 6 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 952 21 MicroFour StrataFrame Base
Warning 7 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1058 21 MicroFour StrataFrame Base
Warning 8 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1332 17 MicroFour StrataFrame Base
Warning 9 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1466 17 MicroFour StrataFrame Base
Warning 10 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1666 21 MicroFour StrataFrame Base
Warning 11 'Public Function EncryptFile(FileName As String) As Integer' is obsolete: 'Writes the encrypted file back to the same location on disk... causes major corruption issues.'. D:\Strataframe\SourceCode\MicroFour StrataFrame Base\XML\XMLBasics.vb 1776 21 MicroFour StrataFrame Base
Warning 12 Could not resolve this reference. Could not locate the assembly "MicroFour StrataFrame Business, Version=1.7.0.0, Culture=neutral, PublicKeyToken=99fe9917f71608a7, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MicroFour StrataFrame UI Expanded
Warning 13 Could not resolve this reference. Could not locate the assembly "MicroFour StrataFrame UI, Version=1.7.0.0, Culture=neutral, PublicKeyToken=99fe9917f71608a7, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. MicroFour StrataFrame UI Expanded
Warning 14 The referenced component 'MicroFour StrataFrame Business' could not be found.
Warning 15 The referenced component 'MicroFour StrataFrame UI' could not be found.

RE: Can no longer step thru framework code

Trent L. Taylor — Tue, 29 Sep 2009 12:44:10 GMT

[quote]I hate to be stupid about this, but I am still a newbie [Smile] Can I just delete the 1.6 assemblies and not do anything else?[/quote]

You are not stupid at all! This is one of those things that once you know you know. But the first time or two may be the learning curve.

Yes. You can delete the SF assemblies from the GAC without any issue.

[quote]To build in debug mode, is all I have to do is handle that in the configuration manager?[/quote]

RE: Can no longer step thru framework code

Marcia G Akins — Tue, 29 Sep 2009 12:35:25 GMT

[quote][b]Trent L. Taylor (09/28/2009)[/b][hr]Yes, you need to remove the 1.6 assemblies altogether if you are not using the 1.6 build anymore. This can cause some issues at times. Another thing that you can do is remove all of the SF assemblies, rebuild the source code (which should add them back in), get out of VS, go back in and you should now be dealing with the compiled SF assemblies in debug mode. Also, I am sure that you already know this, but be sure to build the SF assemblies in debug mode otherwise you will not be able to step into them.[/quote]

I hate to be stupid about this, but I am still a newbie :) Can I just delete the 1.6 assemblies and not do anything else? To build in debug mode, is all I have to do is handle that in the configuration manager?

Thanks!

RE: Can no longer step thru framework code

Trent L. Taylor — Mon, 28 Sep 2009 14:01:07 GMT

Yes, you need to remove the 1.6 assemblies altogether if you are not using the 1.6 build anymore. This can cause some issues at times. Another thing that you can do is remove all of the SF assemblies, rebuild the source code (which should add them back in), get out of VS, go back in and you should now be dealing with the compiled SF assemblies in debug mode. Also, I am sure that you already know this, but be sure to build the SF assemblies in debug mode otherwise you will not be able to step into them.

RE: Can no longer step thru framework code

Marcia G Akins — Mon, 28 Sep 2009 11:19:01 GMT

Hi Trent.

Can we discuss it here please :)

I just got version 1.7.0.2, installed it and rebuilt solutions. I still cannot step through the framework code. But the goofy thing is that versions of the dlls in c:\windows\assembly are still showing up as 1.6.0.0 and 1.7.0.0. Could this be causing the problem?

RE: Can no longer step thru framework code

Trent L. Taylor — Fri, 25 Sep 2009 11:23:01 GMT

Since we are discussing this on the other thread I will leave this alone. But for those who stumble upon this and are curious, the SF source needs to be rebuilt in debug mode after a new install since the assemblies in the GAC get updated with the new version.