I can get an UpdatePanel control working(partial postbacks) no problem with a new fresh .net 3.5 project. I've overcome many of the pitfalls that are answered here on this site. (scriptmanager on the page, using triggers, or placing the button within the panel itself.)
If I have try to use the UpdatePanel on a project that was originally a .net 1.1 project, upgraded to 2.0, now recently upgraded to 3.5, I can't get partial post backs for anything. At this point the code is exactly the same within the form. My relevant web.config parts are the same, and from what I can tell my .proj files too are the same.
Anyone have any ideas here?
Have you checked to make sure you aren't still caching the assemblies? I know the AJAX control toolkit required you to "copy local". Make sure you eliminate that as a possibility.
I've checked, and the copy local is set to false on all references. Any other check to see if caching is a problem?
Related
I'm having trouble with an javascript file on ASP .NET Core 2.0. I'm doing a course to learn ASP .NET Core, and my javascript file doesn't wants to work, I don't know why, it doesn't appears on network and it doesn't shows any console.log that I try to use.
The file is located at wwwroot/js and I have the #section with the script included on the view. I already compared my code with the final project and there's nothing wrong.
What I've tried so far is: resetting browser cache, putting the script on the layout.cshtml, but no results. I also tried to do some other stuff that I found here and nothing worked.
Okay, I fixed my problem, the issue was happening because there were 2 csproj on the same folder, and I was running the one without the javascript file, what a dumb mistake. Thanks for everyone that tried to help me anyway.
I´d like to know if there is any way to edit the codebehind of an Asp.net web application while debugging?
When I try this, a message is displayed on the status bar saying "cannot currently modify this text in the editor. It is read-only".
The application is actually running off of a compiled version of your code. If you modify it it will have to recompile it in order for your changes to work, which means that it will need to swap out the running version for the new compiled version. This is a pretty hard problem - which is why I think Microsoft has made it impossible to do. It's more to protect you from THINKING some changes were made when they really weren't.
I tried changing some attributes of MVC application Site.css but running it doesn't seem to recognize the changes because I don't see any of them in effect. Why is this? I am just new to ASP.NET MVC project development.
Please elaborate on what are the changes you made? Makes sure you are referring the correct version of site.css. Also try Ctrl + F5 to replace your cached version of css.
I have a .NET 4 website in VS2010 stored in a TFS 2010 team project. I need to add a reference to System.Data.Linq.dll to the website. I am referencing a LINQ DataContext that is defined in another project and I get build errors saying that I need the reference to System.Data.Linq. I go up to the "Add Reference" menu option and add it like I would any normal reference, and it even shows up in the Web.config and in the Properties pages for the website... BUT if I build I still get the same error.
So I found a place in my code where I was referencing the LINQ count function and it told me it was invalid because I was missing a reference and it offered to add the reference automatically. I told it to add the reference automatically and it is at this point that I get the error mentioned in the subject:
TF14040: The folder $/Folder/Subfolder may not be checked out. No items were checked out
I've done some research online but I haven't been able to find much. I saw on a blog that making the folder not readonly fixed the issue for him, but it didn't seem to work for me unless I misunderstood something.
I tried loading up the project from source control onto a fresh computer where that project had never been loaded before and I can reproduce the issue the same way. Help would be greatly appreciated.
FWIW, this error also occurs in different circumstances. I had the same error today from the command line when trying to use tfs checkout SomeFolder /login:user,password, although this was not within the context of an asp.net app, I'm currently working on dependency replication. For me, adding the /recursive command worked, like this:
tfs checkout SomeFolder /recursive /login:user,password
The hint to try that came from here, by the way.
I have no idea if this is your problem but I've noticed that TFS2010 seems to have some bug somewhere around folder renames/deletes/changes or something. The bugs seem to go away when you check everything in and try again after the folder change has been saved to source control. I have hit this issue a dozen times this week but don't know exactly what the scenarios are. It's quite frustrating.
I figured it out, but it's a little strange. I had some build errors that I hadn't fixed yet, also my web.config file used to be for a 3.5 SP1 site and I upgraded the site to 4.0. Somewhere along the line the build errors and the web.config combined to form this strange weird error that apparently has nothing to do with TFS.
I figured it out by creating a new website and slowly moving over portions of my site to that new site. Things didn't go totally crazy until I moved over my web.config. So I went back and updated my web.config file so that it more closely matched the way a .Net 4 web.config should by trimming out a lot of stuff and now things are good and building fine. Thanks for the help.
I know I am not running the most up-to-date version of ACT on my server. (I tried to update it recently and it broke a bunch of things.)
So I want to use a control that I have never used before and I need to look at the reference for the control to be sure I'm using it correctly. But I dont know the exact version I am running.
Where can I find this information?
Right click on the AjaxControlToolkit.dll file and view the properties. The version number there will tell you what version you are using.