I am using Visual Studio 2008 ASP.NET Development Server and EPiServer CMS, FF3 and IE7
Edited Question - Removed irelevant distractions as I now realise it has nothing to do with dynamic content.
Every so often javascript files I am working on are not getting fully downloaded. The file I am currently having a problem with is only 49 lines long and is getting cut off with only 30 or characters to go.
Anyone else seen this?
TIA
Pat
Seems to be a caching bug with StaticFileHandler. Check out this blog post and this thread on Episerver World.
Haven't tried it fully yet, but they say setting cacheControl="private" on staticFile should solve the problem "sort of".
<staticFile expirationTime="1.0:0:0" cacheControl="private" />
This is a longshot, but try switching to the ASP.NET StaticFileHandler in web.config.
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 have an ASP.NET website that worked fine using and debugging in VS2008. I went through the upgrade process opening the solution in VS2010. I can run the site, but as I make changes in the app_code folder classes, they don't seem to commpile and warn me of compile-time errors. As soon as I get to a point that calls the class, the errors show up. Sounds JIT I guess, but this isn't how it was working in 08. Is there an option that was changed in the upgrade process? This is a large project, I really don't want to break something and not find out until some obscure page is opened.
I feel like a bit of an idiot, after asking the question, I went to my Configuration Manager and found that the web project was un-checked in the build column. I still don't know why this would have changed from 08 to 10, but everything seems to be working now as it did on 08.
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 am working with an ASP.NET website that is currently being referenced by IIS. When I open .aspx files for editing, the pages seem to hang randomly - has anyone else experienced this? Is there a known cause (and solution)?
Thanks
I had the exact same problem but maybe another cause.
If you use GIT in your visual studio, turn of "Show current branch in Visual Studio".
All of my lag went away in an instant.
Something that seems to exacerbate this problem is non-compliant markup, but it can often happen with control libraries and also happens occasionally with the vanilla controls for no apparent reason.
You might want to change the default to "source view" rather than "design view". You can do this, in:
Tools >> Options >> Html Designer >> Start pages in
Has anyone had experience with VS2008 incorrectly identifying variables in the code-behind as not being defined on the .aspx page? How was this resolved? The page is executing properly without any runtime or compilation errors.
Nevermind. Closing and re-opening the document in question seems to have resolved the problem. Anyone watch "The IT Crowd"? ... haha. "Have you tried turning it off and on again?" Seems to solve everything.
Check out my answer to my question here: Web site reports xxx does not exist in current context after upgrade to VS2008 Sp1
There is a hotfix for this if your getting the same issue I was.