0

There are two pages in a legacy app to which I'm addding fuctionality.

One of the .aspx files, when the "Design" view is shown, sports an Events tab in the Properties pane:

enter image description here

The other, though, does not - it only shows Properties:

enter image description here

I need to add a custom method to this code; how can I create a corresponding .vb code-behind file where I can add this method?

UPDATE

I tried jackjop's suggestions, but F7 did nothing, and I do not seem to have the "Show All Files" glyph:

enter image description here

UPDATE 2

I tried adding this to the top of the .aspx file, mirroring what is in the aspx/aspx.vb pair that works as I want, but it didn't seem to make any difference:

<%@ Page Language="VB" AutoEventWireup="true" CodeFile="custmaint_entry.aspx.vb" Inherits="pages_custmaint_entry" %>
B. Clay Shannon-B. Crow Raven
  • 8,547
  • 144
  • 472
  • 862
  • hmm, maybe [this](http://stackoverflow.com/questions/28058093/visual-studio-2013-show-all-files-button-is-missing) can help – sertsedat Apr 10 '17 at 15:43
  • 2
    You can delete the .aspx page, then re-add it, making sure this time to choose the one that adds the code behind. Then copy your markup back into the .aspx, making sure not to erase the code behind related stuff in the @Page directive. Alternatively, create a text file manually and then include it in your project. If VS doesn't automatically nest it you can modify the .vbproj, following the format of the other code behinds. – mason Apr 10 '17 at 15:44

2 Answers2

2

When you create an ASPX file it also creates a code-behind file. You just can't see it.

From aspx file press F7 or click Show All Files button in Solution Explorer.

enter image description here

Notice that when Show All Files is not clicked, it doesn't show code behind files.

enter image description here

Or you can just simply right-click on aspx file on Solution Explorer and click View Code. If this also does not work, then you probably deleted the code behind files, I suggest you re-creating every file.

sertsedat
  • 3,490
  • 1
  • 25
  • 45
1

The issue here is that the solution was created from a precompiled and deployed application and the code behind files do not get deployed. I can also see many "Copy of" files littering the solution.

I am posting because this is typical in many legacy applications -- the original source code needs to be located -- you cannot modify precompiled code without the source. (Well, you can however you will have to rewrite ALL of the code behind and other custom DLLs). And NO, a "decompiler" is of no use here.

This is what I am doing on my own legacy code, but -- it is a piecemeal task and whether it is better than starting all over is debatable. Unfortunately, the real fix would be for enterprises to maintain a full source code repository.

jinzai
  • 436
  • 3
  • 9