vb.net - .NET debugging an existing project -

background / disclaimer

first of all, please feel free skip entirely if can understand questions below.

i'm still fresh new .net, elder monkey on bad old asp in regular vb.

i got company legacy .net vb files , have couple of huge projects, on 50mb of files , 1gb whole project , debugging them haven't been easy. i've read through w3schools tutorial , did many google researchs point in can't make work. , unlike in similar question don't think simple issue.

i don't know if projects mvc or regular web application, told use "other project types > visual studio solution > blank solution" , "add existing web site" that. no further instructions or orientation, see have dlls , makes me believe not mvc.

anyway, whichever or many other ways i've tried add files visual studio, never use debug 1 of them. 1 works fine enough, can @ least see running locally alike webserver. other gives me many random errors , warnings "compile" debug , run on visual studio's own server (i think it's called "asp.net development server"). errors shouldn't exist "the file xxx doesn't exist" while can verify does exist!

i don't expect have here, still hope find some. sorry if much.

questions

• what options have debug big visual studio project works online in server have debugging , error options turned off?
• how can know how "import" existing project visual studio begin with?
• is homework question?
• (new) given have 3 places sync many files (local, shared production network , live) what's best approach work on , debug existing errors? out of box thinking welcome (converting project, not using visual studio, older version, whatever)

sounds might little bit on head. first step ask dev there out because in real learning ride.

before go further, working local copy.. not server one, right? if have browsing across network server, need stop right now. instead, copy of files local directory , work it. go learn publishing. working directly off of server bad thing(tm). screws debugging and, more importantly, it's plain wrong. companies have type of source or version control system in place. use it. if it's not there, might want bring up.

the add existing web site feature adds web site project, not web application or mvc app. these 3 things different each other. i'm going take guess don't have mvc app based on age of application.

the best way tell difference between other 2 types whether or not .proj (project) file exists in root of site. if there, web application. if not web site.

for web application
if web application, in parent folder see if there .sln (solution). if so, open in visual studio.

if .sln doesn't exist (or project isn't in it) can create new blank solution , click add existing project. there browse .proj file , add it.

at point in solution explorer see if can find of files. likely, missing ones not included in project. if don't see them, click on "show files" button @ top of solution explorer. locate them on, right click, , add project.

web applications not have edit , continue have whole lot of other features why no 1 uses web sites anymore.

for web site
create blank solution, click add existing web site. browse folder containing site , click add.

turning on debugging/errors
debugging , error options purely in web.config. change local config , run again via f5.

one final note
highly suggest once determine whether web site or web application , before begin trying debug beast create own web site/web application test. find tutorial on this, there many. might go asp.net site , watch training videos.

use build couple web pages navigation , maybe database connectivity. might take couple days learn lot more before .net in time.

update new question
not best, only place should debugging off of local copy. debugging on shared file set doesn't work (lots of security problems network drives) never mind fact multiple devs might working out of shared area , debugging off of live production server huge no-no.

now people might there times when have debug in production. reality issues found only in production fall 2 categories: 1. aren't testing right data. - means test environment needs better. or 2. environment issue. best way solve #2 have staging server absolutely identical production final testing on before pushing live.

if still think have debug in production, consider impact of making slight change kills site. sure can roll change quickly, how many people did totally piss off. more importantly how many of them customers and/or execs?

which leads final piece. if project web site project, go ahead , upgrade web application project. when deploy, shouldn't copying code out there. instead, ought compiled.