Member Avatar for karthik_cud

Hi, im working on my college library management system created by someone i dont know, the problem is the changes i"ve made has no effect on the output whenever i run this application, i think the person who have developed that application has locked the code and prevented it from editing so help me to finish this stuff..............

  • 3 Contributors
  • 2 Replies
  • 94 Views
  • 13 Hours Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

As and started to look at runtime/environment causes, here is a focused, practical checklist for ASP.NET/VB.NET projects when edits produce no visible effect. These checks avoid repeating earlier suggestions and target a few common but often-missed causes (precompilation, project settings, deployment copies, and compiled/assembly mismatches).

  • Confirm project type and precompilation. A Web Application compiles code-behind into assemblies in the project/bin folder; a Web Site can be precompiled so source edits have no effect. Look for a PrecompiledApp.config or for missing App_Code sources — if the site was precompiled without the "updateable" option, the source will not change behavior.
  • Verify file is part of the project and set to compile. In Visual Studio the .vb file must be included in the project and its Build Action should be "Compile" (not "Content" or "None"). Linked or excluded files can look editable but never get built.
  • Check page/class wiring. Ensure the .aspx directive's Inherits value exactly matches the namespace/class in the code-behind (and that the class is declared Partial). A mismatch can let a prebuilt assembly satisfy the page instead of your edited code-behind.
  • Search for duplicate copies. Use a solution-wide search for a unique string you add; editors sometimes open a file from a copy or a deployed folder. Also check automated publish/post-build steps that may overwrite the bin after you build.
  • Force a fresh runtime compile. Delete the project bin and obj folders and clear ASP.NET Temporary Files for the CLR version in use, then recycle the app pool or restart the development server. Check the timestamp on the rebuilt assembly in bin to confirm a new build.
  • Consider assembly placement and binding. If a strong-named assembly with the same types is in the GAC or there are bindingRedirects in web.config, your local build may be ignored.

Quick verification: add a tiny, unique visible change to an .aspx markup (a short text token), save, and load the site from the hosting folder. If the token does not appear, the running site is using a different copy or precompiled output. These focused checks will narrow the cause without needing to step through code first.

Recommended Answers

All 2 Replies

Member Avatar for wildgoose

I'm not up on Visual Basic, but could the file be write protected?
Is a COM type object wrapped in a DLL and the DLL isn't where you think it is? Application is looking in one spot and the DLL being built is in another? Release versus Debug difference?
Just throwing some ideas out there!

Member Avatar for sknake

That doesn't make sense. You say you have edited the code but the changes make no effect? Step through the code with the debugger and see if it is running the code. You may have changed the wrong method?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.