I maintain an old ASP.NET WebForms application, written using VB.NET so long ago that no one knows who started this application. The guy who maintained it, before I was given it, left before I joined. He didn't put anything in any source control, and he had his PC reimaged. So, I had to piece the thing together from bits and pieces he left scattered around our network. I've been trying to get this to build using a GitHub self-hosted runner on one of our servers. I had a lot of errors, which with help here on Microsoft Q&A, I've been able to reduce most of the errors. The errors I've got left are related to building the app and some odd ones related to Visual Studio. (I am using VS 2022.) Here are the errors: Severity Description Project File Error could not find library 'C:\GitHub\Prod\FP_Timetrack\WicReports\bin\WicReports.dll' WicLibrary C:\GitHub\Prod\FP_Timetrack\WicLibrary\vbc Error could not find library 'C:\GitHub\Prod\FP_Timetrack\WicReports\bin\WicReports.dll' timetrackreports C:\GitHub\Prod\FP_Timetrack\timetrackreports\vbc Error Could not get dependencies for project reference 'WicReports' TimeTrackSite Error Could not get dependencies for project reference 'timetrackreports' TimeTrackSite Error Could not get dependencies for project reference 'WicLibrary' TimeTrackSite First off, I don't understand the first two errors at all. I have removed the reference to the WicReports.dll, twice. Then put in a reference to the VB.NET WicReports project. But each time Visual Studio puts back in the link to the DLL! Why??Second problem, I don't get the third, fourth, and fifth errors. As you can see, there's no referenced file. And it looks even weirder in Visual Studio solution: As you can see, there IS no References folder with references in it, as there are in all the other projects in this Visual Studio solution. TimeTrackSite is the web app, the other 8 projects are helper projects for this convoluted application. So, how do I fix this?

Do you have all this in a project file or are you just browsing the folder structure in VS? You are going to need a web project to support this. A long, long time ago VS supported creating web sites by just using a folder but this was basically abandoned. If you do not yet have a web project then create a new web project first. Otherwise none of this is going to work. What version of the framework was the site written for (it'll be in the project file if you have it or the web.config otherwise). You'll need to upgrade it to at least NET Framework v4 before VS will even remotely want to do anything with it. I don't know what the WicReports binary is (third party? project?) but it appears it was a third party binary that the code referenced. If you have the site running now then that binary is wherever the site is running at. If not then find the binary and put it into a folder in the project (e.g. libraries ). Then in the project's references in Solution Explorer remove any references to this binary under References and then add a binary reference to the version in your new folder. Note that I'm assuming the old binary is compatible with NET Framework v4, if it isn't then things aren't going to work. Your remaining "could not find references" indicates to me that you don't have a project file so adding one will fix that. If you have to create a new project file then you'll need to move all the existing code into it. By and large you can copy all the .aspx/ .aspx.cs/etc files directly into the project by dragging and dropping them. All the code under App_Code, content, etc can also be done that way. The files under App_Data are likely just data files so you'll have to review them. If there are files there then either you'll need to copy them as well or they will need to be recreated (e.g. a database). For the config file you'll need to merge any customizations in the original file with what is now in the project. This is a line by line process. After you've done all that then try to build again. As a final note, if you were targeting pre-NET Framework v4 in the old code then migrating to NET Framework 4 (required by VS) will require yet more changes.

An old ASP.NET WebForms app won't build due to missing references and related

Falanga, Rod, DOH 80

I maintain an old ASP.NET WebForms application, written using VB.NET so long ago that no one knows who started this application. The guy who maintained it, before I was given it, left before I joined. He didn't put anything in any source control, and he had his PC reimaged. So, I had to piece the thing together from bits and pieces he left scattered around our network.

I've been trying to get this to build using a GitHub self-hosted runner on one of our servers. I had a lot of errors, which with help here on Microsoft Q&A, I've been able to reduce most of the errors. The errors I've got left are related to building the app and some odd ones related to Visual Studio. (I am using VS 2022.) Here are the errors:

Severity	Description	Project	File
Error	could not find library 'C:\GitHub\Prod\FP_Timetrack\WicReports\bin\WicReports.dll'	WicLibrary	C:\GitHub\Prod\FP_Timetrack\WicLibrary\vbc
Error	could not find library 'C:\GitHub\Prod\FP_Timetrack\WicReports\bin\WicReports.dll'	timetrackreports	C:\GitHub\Prod\FP_Timetrack\timetrackreports\vbc
Error	Could not get dependencies for project reference 'WicReports'	TimeTrackSite
Error	Could not get dependencies for project reference 'timetrackreports'	TimeTrackSite
Error	Could not get dependencies for project reference 'WicLibrary'	TimeTrackSite

First off, I don't understand the first two errors at all. I have removed the reference to the WicReports.dll, twice. Then put in a reference to the VB.NET WicReports project. But each time Visual Studio puts back in the link to the DLL! Why??Second problem, I don't get the third, fourth, and fifth errors. As you can see, there's no referenced file. And it looks even weirder in Visual Studio solution:

User's image

As you can see, there IS no References folder with references in it, as there are in all the other projects in this Visual Studio solution. TimeTrackSite is the web app, the other 8 projects are helper projects for this convoluted application. So, how do I fix this?

Albert Kallal 4,896 Reputation points

2024-05-08T23:15:54.4966667+00:00

As noted, this looks like a older "web site", and thus no real project file exists. However, you can still right click on the bin folder, and choose "add references".

Hence this:

So, note how the above shows existing references. So, references are to be placed in the bin folder, and thus you are either missing that .dll, or you not referenced it. You need that .dll, and then using references, you can browse to the .dll, and that will "copy" the .dll to the bin folder for you.

So, unlike a asp.net web site project, a older "web site" does not have a nice references page, and for the most part, then references are all dumped into the bin folder. This is not all that great, since then you can't clean the project, or say using GitHub and pull the repo, since in most cases, the bin folder files are ignored.

Regardless, there is a references window if you right click on the bin folder.

Depending on how experienced you are with this code base, I would suggest you convert the project to a asp.net web site, since your build, setup of references etc. is not only far more robust, but can all be done from the standard references page that such projects have.

However, if not done a conversion from a web site to a project in the past (most of this process can be automated), then I don't recommend doing this until you done it a few times, and thus know what you up against.

Right now, to get the build working you need to find that .dll, and best you copy it to the bin folder by using add reference (it will copy the .dll to the bin folder for you when you do this).
Lan Huang-MSFT 26,121 Reputation points Microsoft Vendor

2024-05-09T05:56:56.1966667+00:00

Hi @Falanga, Rod, DOH,

I recommend that you first clean and rebuild the solution and if that doesn't work, manually remove the DLL from the website project (Bin folder). Remove the DLL and build the solution again.

I think you can try Open the Website proj file in notepad and check the reference etc.

When you get the error message "Could not get dependencies for project reference", one of the possible causes could be that you are referencing another project in your solution which has a Target framework not compatible with the target framework of the referencing project.
Falanga, Rod, DOH 80 Reputation points

2024-05-09T14:18:31.06+00:00

Albert, if I convert this from a "web site" app, to an ASP.NET Web Project app, then would it be better for me to create a new Visual Studio solution, then copy everything in the TimeTrackSite project, except the .vbproj file, into the new solution? (And the other 8 projects that are in this solution.)
Falanga, Rod, DOH 80 Reputation points

2024-05-09T16:08:07.9+00:00

Hi Albert, I have removed the WicReports.DLL from the TimeTrackSite project's bin folder. Then did a solution clean and rebuild. And set the WicReports project to the reference within WicLibrary and timetrackreports projects. However, the rebuild still reports not being able to find WicReports.dll for either WicLibrary or timetrackreports. And WicReports.dll isn't in C:\GitHub\Prod\FP_Timetrack\WicReports\bin folder. Of course, I don't want it to use the DLL, but the project as the reference. And yet it still keeps going back to that DLL?!

I don't know if this will make a difference or not, but I did find a log of .resources files in a folder named C:\GitHub\Prod\FP_Timetrack\TimeTrackSite\obj\Debug, which oddly enough is in the GitHub repo, even though the obj folder is meant to be ignored in the gitignore file. That may mean nothing, and I don't see a WicReports.resources file in that folder.
Falanga, Rod, DOH 80 Reputation points

2024-05-09T17:01:33.48+00:00
WOW! I added double what was saved to the reply I made immediately above. I wish this forum would give you warnings about exceeding the character limit.

OK, making this smaller. If you have any questions, please ask. For the TimeTrackSite project, the .vbproj file has this:

<TargetFrameworkVersion>v2.0</TargetFrameworkVersion>

however, when I click on the Property Pages for TimeTrackSite, it shows it targeting .NET Framework 4.5.2. I can't explain the discrepancy and am not sure which is really being used.
Albert Kallal 4,896 Reputation points

2024-05-09T17:32:44.79+00:00

convert this from a "web site" app, to an ASP.NET Web Project app, then would it be better for me to create a new Visual Studio solution, then copy everything in the TimeTrackSite project,

Yes, but, you don't manually want to copy the files!!

So, yes, I recommend hands down you create a fresh new project.

You THEN use in that project add->existing, and select the file(s) from that existing site.

You probably should do this one folder at a time. In other words, if there are several folders, then I would in the new project create the new folder (add folder), and THEN right click on that folder, and use add->existing file, and then browse + select those files.

Once you have ALL files (don't worry about references just yet), then you choose:

Note that ONCE you use that option, it will go away!!!!

And this option does NOT appear when you open the original project! And the option will ONLY appear AFTER you used the add->existing file option!

Note that use of this option will thus automatic change/convert/modify the page directive of each file you imported. (from CodeFile="bla bla bal" to CodeBehind="bla bla bla".

So, yes, I think it is a REALLY great idea to try this.

After you have done the above, then you can now include (add) the other projects. Obviously then, I would ensure that I have the other projects that create those .dll's for you setup and working (building) before you attempt the above.

So, if have those project(s) that builds + creates those .dll's you are to include in this new project? Then of course, get those projects building first. They should be quite easy, since they of course are not likely to be web sites or some such, but only projects that are of a class type, and thus they should be easy to setup. So, for ANY of those projects you plan to include, then get those building and setup first (and thus assume they build ok).

So, yes, I high recommend you start a new fresh project. But, I do NOT recommend that you wholesale just copy the files - ALWAYS use the right click on project, and choose add->existing file. As noted, I would probably do this adding folder by folder, but of course adding all the root files first.

Once you add those files, then the context menu above (convert to web site should appear). If not, then take a quick look at any .aspx file in the older project. If you see CodeFile=, then that WAS and is a web site, and for web site applications, the page directive will have CodeBehind="".

As a FYI? When you done the above, and start including the other projects? guess what? You WILL WIND UP with a .dll assembly reference to the bin folder of that other project!!!

It just at build time, then each of the included projects will build first, and THEN the .dll's from those included projects will be copied to your main project bin folder, and THEN you main project builds.

So, the above is a "subtle" issue, an near one of semantics. So, note that JUST including the other projects does not automatic resolve references for you! (read this again!!).

Only until you right click on references, and choose the assembly (check the box) will that .dll REALLY be included your project.

And NOW if you go look at the project references, you WILL see a direct reference to the .dll's in each of those projects, and the direct reference WILL BE in the other projects bin folder! I point this out, since in near all cases, you ARE told to not reference those .dll's directly, but in fact when you include those other projects, the end result is you wind up directly referencing the .dlls in those other projects. However, since you now included those projects, then at a build time, those external .dlls are now copied to the current projects bin folder at build time. So, in effect, a included project gets you automatic build of those .dll's but it DOES NOT remove the fact that you have those .dll's directly referenced in their respective bin folders!

So, you can actually just go and add the reference from the bin folder, or you can right click on the references in the project explorer, but BOTH approaches still result in the project directly referencing the external .dll's in their respective bin folders!
كوثر بنت عوض بن قاسم اليافعي 0 Reputation points

2024-05-09T18:02:11.7666667+00:00

يفضل التوضيح بالفيديو
Falanga, Rod, DOH 80 Reputation points

2024-05-09T19:26:20.58+00:00

Your approach seems good, Albert. One thing that bothers me, that I've only just discovered, is someone has removed supported .NET Frameworks from the web server?! Back in 2015 I took a picture of the installed .NET Frameworks on that server, using RegEdit. They had everything from .NET Framework 2, to 4.8 on that server. Today, all supported .NET Frameworks have been removed and only unsupported .NET Frameworks remain?!

I don't get it, why intentionally remove supported .NET Frameworks and only leave behind unsupported .NET Frameworks?
Falanga, Rod, DOH 80 Reputation points

2024-05-09T19:57:58.89+00:00

Albert, you're right, each .aspx file CodeFile= in them. None of them have CodeBehind=. So, regardless of what the project property page says, this is a .NET Framework 2 app.
Albert Kallal 4,896 Reputation points

2024-05-09T20:39:33.9033333+00:00

Not quite. The fact of CodeFile vs Codebeind?

This is NOT a factor of what .net framework.

This is an issue of a "web site" vs a "web site application".

So, the .net framework does NOT determine this issue. What determines this issue is if you have a web site, or a web site "applicaton". as above shows, you can (and should) convert the web site to a web site application. Doing so will thus result in your page directives being changed from codeFile to CodeBehind. This change in fact occures when you use the "convert to web application" above. (or you manually change each page).

So, don't confuse the issue of what .net framework vs that of a "web site" vs that of a "web site application". All of the choices for .net 2 all the way up to .net 4.8 support both types of projects.

why intentionally remove supported .NET Frameworks and only leave behind unsupported .NET Frameworks?

We don't know, but it very possible that a whole "image" of the computer was made in case of needing to upgrade, replace or restore a damaged computer, or the web site was damaged at one point in time. And that image may well have been made before you grabbed that screen shot and information. So if that server failed, or had everything re-installed? (which can day a full day), then perhaps a full image was restored - which takes < 30 minutes, and then the server is good to go again.

Now, in my previous comments, I stated that attempting to include the other projects should be a breeze and easy, since I assumed those other projects were not web projects, but only shared code. However, it looks like (for some strange reason), that each of the reports required resulted in a whole new web site being created, and then each web site was added to the main server. However, that does NOT mean that multiple projects were included into one project at any previous time.

Remember, in IIS, you can define each folder as to be a 100% its own web site, and then go off and create a whole new web site. You then work on that site, build it, and then deploy the WHOLE site to a sub folder. This seems to be what had occurred in the past. (and keep in mind, from IIS, then you can set/define that new folder to be a whole new site, and NOT just a sub folder of the main site. So, once again, the fact of multiple folders and multiple sites existing on the server DOES NOT suggest, hint, nor necessary imply that the orginal project had multiple projects in one project file. And given that you suggested that the existing page directives don't have CodeBehind, then almost for sure, you NEVER had a main project with multiple projects included. So, each time a new report was created, then a whole new project was created. Then from IIS, that new folder was defined as a whole new site, and then that new report as a whole web site was deployed to the sub folder. So, you never had one project, but each report was a 100% separate project, and at no time were they ever combined into one project.

Of course, converting the one main project into a "application" makes the most sense, but that STRONG suggests you not attempt to add more web projects to the one web project (and I don't recommend you do this anyway). You suggest that about 10 such sub projects existed, but they were never actually included in one main project. They always were seperate, and it looks like they all were actually separated folders, and then in IIS, the single folder was setup as a full web site.

Not seeing and knowing the details, but this does suggest that each of those 10 projects should be combined into one project, especially if each of them is only 1 or 2 web pages. If each project is more complex, then of course I would leave them as 100% separate for the time being.

However, to combine the projects into one project, then that changes things here, since each separate project was never really part of one project build, but each had their own full project for that one folder.

So, in theory, if you attempting to combine everything into one project, then you not use multiple web projects (regardless if they are web site, or web site applications).

So far, it looks like it makes little sense to have multiple projects into one project, but looks to make MUCH sense to pull those sub sites all into one project.
Albert Kallal 4,896 Reputation points

2024-05-09T21:01:31.37+00:00

No, the fact of Codebehind vs that of Codefile has nothing to do with the .net framework choice. From .net 2 to .net 4.8, either project type choice is supported.

Edit, I see my deleted post has returned, and thus I removed all of my text in this near duplicate post.
Falanga, Rod, DOH 80 Reputation points

2024-05-09T21:05:53.5633333+00:00

Yeah, something is weird about this forum, Albert. One of my posts from today has never appeared.

I didn't express myself clearly. What I meant to say is that all the .ASPX files only have CodeFile in them. None of them have CodeBehind. As I understand it, that implies that the app is a "web site" app, not a Web Application app. If I've said this wrong and misrepresented reality, please correct me!
Albert Kallal 4,896 Reputation points

2024-05-10T05:25:37.9366667+00:00

That is 100% correct on your part.

But your post hinted that because you see CodeFile, then this must have been .net 2.0. (and as I stated, that not necessarily the case). However, the fact of seeing CodeFile MOST certainly means that was a web site. And as noted, this thus means it going to make little sense to try and combine multiple "application projects" into one project, since that's not what you could have possible had in the past.

Hence, this suggests that converting the one main project to a "application" is a good idea. As for the other 10 or so web sites?

It is not clear why they were separate, but given they are simple, and 1 or 2 pages, then I would as noted, likely just import those files into the one new project. There MIGHT be some reasons for those separate projects (such as connections to a different database for each of those 10+ web sites). If that is the case, then you have to come up with a means to have different connections for each of those sub folders. (that can be a challenge, but workable).
Falanga, Rod, DOH 80 Reputation points

2024-05-10T14:00:45.18+00:00

I confess I did have some confusion about CodeFile and .NET Framework 2.0. But I realized that the real issue is a web site architecture, which I think is now broken. I really wish there weren't so much resistance to upgrading any project, here. It's like once an app is released to production, nothing must ever change it. I'm going to argue with my boss for the umpteenth time, to upgrade this app to a supported version of .NET Framework and consistent throughout.

The app is confusing. I've seen a method in the web project, call out to another method in a different project, and the only thing that method did was call another method in a third project. It was like they were using the separate projects as library assemblies, although they aren't. Well, if all I can do is convince my boss to let me upgrade the .NET Framework and make them consistent, I'll have to accept that. Rewriting the thing is too much to hope for.
Albert Kallal 4,896 Reputation points

2024-05-10T22:28:36.3666667+00:00

The information about one web project calling a web method in another project VERY much confirms my guess in regards to that each folder was a 100% separate project, were never one project, and were never combined into one project. This explains the 10+ separate projects. And this also explains WHY some web method calls were used (since in theory, each web site is not aware of the other sites!).

And this means/suggests that each folder in that web site was setup to be a 100% separate web site from a folder point of view. (you go into IIS and set that folder as a web site, and this as noted is allowed in IIS - and the folder thus has to be defined as a web site folder - not a regular folder of the root site).

As a result of the above information, then it makes little sense to combine all sites into one project unless you willing to modify each of the 10 sites to work based on the assumption of having only one web site as opposed to 10+ nested sites.

In other words, trying to combine all the sites into one will break existing code and assumptions made way back then.

I would thus just ensure that each of the 10+ projects build correctly. I would then setup the main site, and then create a new folder for each of the sub sites (of which from IIS you define and setup as a web site folder - not just a regular folder).

2 answers

Michael Taylor 49,071 Reputation points

2024-05-08T21:34:00.7933333+00:00

Do you have all this in a project file or are you just browsing the folder structure in VS? You are going to need a web project to support this. A long, long time ago VS supported creating web sites by just using a folder but this was basically abandoned. If you do not yet have a web project then create a new web project first. Otherwise none of this is going to work.

What version of the framework was the site written for (it'll be in the project file if you have it or the web.config otherwise). You'll need to upgrade it to at least NET Framework v4 before VS will even remotely want to do anything with it.

I don't know what the WicReports binary is (third party? project?) but it appears it was a third party binary that the code referenced. If you have the site running now then that binary is wherever the site is running at. If not then find the binary and put it into a folder in the project (e.g. libraries). Then in the project's references in Solution Explorer remove any references to this binary under References and then add a binary reference to the version in your new folder. Note that I'm assuming the old binary is compatible with NET Framework v4, if it isn't then things aren't going to work.

Your remaining "could not find references" indicates to me that you don't have a project file so adding one will fix that.

If you have to create a new project file then you'll need to move all the existing code into it. By and large you can copy all the .aspx/.aspx.cs/etc files directly into the project by dragging and dropping them. All the code under App_Code, content, etc can also be done that way. The files under App_Data are likely just data files so you'll have to review them. If there are files there then either you'll need to copy them as well or they will need to be recreated (e.g. a database). For the config file you'll need to merge any customizations in the original file with what is now in the project. This is a line by line process. After you've done all that then try to build again.

As a final note, if you were targeting pre-NET Framework v4 in the old code then migrating to NET Framework 4 (required by VS) will require yet more changes.
Please sign in to rate this answer.
Falanga, Rod, DOH 80 Reputation points

2024-05-09T16:38:59.3466667+00:00

Hi Michael, you've brought up a lot of good points and suggested directions for me. I'll respond to some here.

I don't know what version of the .NET Framework this app was originally written in. Whoever started it and the guy who last had it before it was dropped in my lap back in 2015, didn't put it in any source control. Instead, they left it scattered around on five different servers, and not altogether. I had to put it together as best I could in 2015. It does bring in Federal grant money (we're a state government department), but fortunately it isn't used often. I don't remember too clearly back then, but I think it was originally a .NET Framework 1.1 app, but I'm not entirely sure. Looking at the project that is the web site (TimeTrackSite), in its .vbproj file, I see this line:

<TargetFrameworkVersion>v2.0</TargetFrameworkVersion>

So, at least that project is at version 2.0.Just for a bit of background. Whoever the original developer(s) were, they didn't write this in typical WebForms practice, like putting connection strings and other secrets into the Web.Config file. Instead, they treated this app like it was a console application and put all secrets into an INI file that was stored in the machine's Windows\System folder.

Now for some more pertinent background. This app is visually very simple. It consists of 10 or 11 pages; that includes the pages for reports. However, the original developers used 9 separate VB.NET projects to implement 10 web pages. There are some instances where page A in project A, calls a method in Page B of project B, which calls a method to invoke a method in page C of project C, which brings up a page D in project D. So, both projects B and C are just passing the invocation along to somewhere else. Back in 2015 I asked my supervisor if I could rewrite this app, because it is needlessly complex. He said, "NOOOOOOOOOOOOOOOOO!!!!!!!!!". And at this point I began to realize that there is a HUGE RESISTANCE to ever modifying any application, once it is written. Thus, increasing our technical debt considerably. We may have reached the point that sometimes happens where an app is broken beyond repair, so a rewrite or at least upgrading the underlying technology, is necessary. I've occasionally seen this happen and it always results in resistance until it can no longer be avoided.

One other important point you made, concerns the WicReports project. It is a project that is a part of this solution. This solution would build fine on my old PC, which I got used back in 2015. It does not build on my new PC. It is one of those examples of something that "runs on my PC", but really are dependent upon whatever environmental conditions exist on the old PC. I hate that, "it works on my PC" argument. As someone who loves to have consistent, automated builds and deployments, this mentality of having to have some old PC under someone's desk, just so they can build an app because it cannot be done anywhere else, sucks.

I'll look into the App_Data folder and the App_Code folder, to see what's there and if I can move whatever is in App_Data to somewhere else for safe keeping.

كوثر بنت عوض بن قاسم اليافعي 0 Reputation points

2024-05-09T18:02:59.6466667+00:00

في حاله نسخ ملف والتعديل عليه بدون انشاء

Michael Taylor 49,071 Reputation points

2024-05-09T18:15:48.7+00:00

The app is targeting .NET Framework 2. VS 2022 won't load it and upgrading to .NET Framework v4 is a pretty big change. I'm still going to recommend that you just create a new NF 4 ASP.NET WebForms app and copy things over. It'll be less error prone. Additionally a lot of your original dependencies will have to be updated otherwise they won't work at all because NF 2 and 4 are not backwards compatible.

This project looks like the old TimeTracker app that MS published as a template project for tracking time way back in the v2 days. We actually used it for a while and upgraded it before we migrated to something else. Your version looks customized. Is there anything in the solution that is confidential besides connection strings?

Honestly I don't generally recommend it but upgrading this really old project is going to take some serious effort and understanding about the differences and what to change and what not to. Unless you're really comfortable with this then it might require you to do some studying on everything that is going to be involved. If you have anyone on your team that could help you it would probably go a long way. If it is completely non-proprietary then you could also post a subset of the files online and perhaps we can help guide you on what to change.

Falanga, Rod, DOH 80 Reputation points

2024-05-09T19:31:53.6433333+00:00

Yes, Michael, there are other confidential information in the source code. I wrote about that in a post, which this forum software wouldn't allow me to publish. Too long, I guess. Anyway, the original developers hard-coded accounts that could do administrative actions. There are other, worse things they did.

I'm beginning to wonder if I should just go to a different project, more up to date. I'm trying to prove that we can use GitHub self-hosted runners to deploy in house. Trying to fix an old app that I've already been told not to update, seems like I'm fighting a losing battle. (There's HIGH RESISTENCE to ever updating anything here.)
Sign in to comment
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

An old ASP.NET WebForms app won't build due to missing references and related

2 answers