I wanted to make a small test site using the Metro UI framework (http://metroui.org.ua/)
So, I started up my newly installed Visual Studio 2013 and started a "new website". I added the neccesary css and js and made a very basic masterpage and default.aspx. But here comes the problem: the css does get loaded, but it doesn't get applied. Not in FireFox, not in IE, not in Chrome and not in the "Page Inspector".
It's quite weird, because in my previous VS2012 this same workflow for testing and experimenting with a framework just worked. I really can't find the problem. Maybe it has to do with my new Windows 8.1, my new Visual Basic 2013, maybe an programming error (although that would be very unlikely, since I checked everything).
I also tried installing the framework using NuGet instead of manually adding it. Same result: it does load, but it doesn't get applied.
Anyone knows what's happening here?
Thanks in advance!
According to MetroUI you have to follow 5 simple steps
Create page with HTML5 DOCTYPE
2.Include metro-bootstrap.css
Include metro.min.js (jquery.js required)
Create main container with class .metro
Use markup, as described in the pages of this site
In your posted images I can't find a container with class .metro . I'd really check the sample code from the posted page.
In case I misunderstood anything please let me know!
Related
I just tried to install this framework through the Visual Studio Community's NuGet and I linked appropriate dll, so this is what I got:
Still, things like MetroContextMenu or MentroMenuStrip are missing...Probably some more that I am not aware of.
What would be the correct way to install this framework? What am I missing?
I am using Visual Studio Community and a Winforms based application.
I guess you ended up having the controls that are found in this repository
The original guy must have removed a number of controls due to some bugs and issues, though i dont think so that there was a MetroMenuStrip provided.
You are missing some more controls like :
MetroGrid
MetroDateTime
If you want to get those controls as well, here is the link to a repo someone has been maintaining.
I dont think so that you will get a MetroMenuStrip or maybe you can go through the Git history and check to see if they had the source code back in time.
If you want to create your Custom MetroMenuStrip, This guy has done something similar.
Best of luck.
I am trying to insert data to SQL server table with using C# ASP.NET. I watched a lot of tutorial video. If I create a button and double click on it, I see quite different codes from videos and other tutorials.
To make clear my problem, I added my and tutorials' code screenshots.
What shoud be the reason and how can I fix it?
This is from tutorials:
This is from my VS 2013
You used a Visual Basic template to create your project. Notice the source file in your screenshot is Default.aspx.vb. You'll need to create the project using the C# template.
Edit: I changed the screenshot to New Web Site instead of New Project.
I am working on a Web application project and although I am an experienced Visual Studio developer almost all of that has been in WinForms, console apps, Services, etc. That is, I have very little experience with using VS to develop web pages (Web Forms, asp.net, etc.), however, I am learning how to apply my previous Web page knowledge to VS.
One thing that has been throwing me for a while is how to apply additional CSS files in development, that should not be used in production (because they are already there). Specifically, I am working on a set of pages (DNN module) that is being deployed into a larger website context.
This all works fine, except the VS Web Page Design Editor is nigh useless because it's WYSIWYG rendering is not even remotely close to what the page looks like on the site. I know why this is happening: the site (and DNN) have their own set of CSS files that are getting applied/added to the page.
I know that I could just add those same style sheets to my web page in development (using <link href=...> tags?), however, then the web page would be deployed referencing these CSS files twice (there's a bunch of them too).
So my question is, is there any easy solution to this? Is there some setting somewhere that I can just say "use these additional CSS files in development or in the Design Editor"? (I hHve tried to google this, etc. but I just find dozens/hundreds of articles about how to add or edit CSS in Visual Studio)
Unfortunately I think that may have mis-explained my need somewhat. The issue really is not a development vs production issues, but rather an IDE vs execution issue. When debugging the code or otherwise running it in development, it is still within the DNN test environment we have setup, so it does have the extra file even here.
This is really about the HTML designer, when i am using it it does not have these extra style sheets, so I cannot see what the work I am doing really looks like. Instead, i have to run it every time I want to see whether any change i make looks like it is supposed to. This gets extremely onerous, especially with how slow DNN is to compile and reload.
Hmm, do you have your web project setup to run on IIS instead of IIS Express?
Something I do is often just work in the project then Save and if needed build. Then browse to the Site on my machines IIS instance (right click file in solution explorer and select browse if using ASP.NET Web forms).
Once I have done that I can refresh my page. I also use #if Debug in my code to bypass user login and etc to make round tripping faster...
We have an ASP.Net application, done by a third-party, that uses third-party controls. The problem is that some of these controls don't work with anything higher than IE8. I have been asked to look into this and try to figure out a way to make them work again (the company is upgrading to IE11).
Unfortunately, the source code is not available; there are no code-behind that I can work on. And the controls are no longer supported.
One solution that I can think of is adding a new .aspx page and use inline code/javascript/code-behind to return the functionalities that are not working.
This is my question: is this feasible? Or are there any other ways that I can resolve this, short of replacing the application with a new one?
Thanks.
I ran into a similar problem a while ago and resolved it by decompiling the controls via a decompiler tool like .NET Reflector, making the necessary changes, recompiling and uploading back to the server.
How do you understand "No control over your namespaces" namespace issue, quoted from,
http://reddnet.net/code/asp-net-web-site-vs-web-application-project-part-2/
Here are more background:
one of the cons of web site project type of VSTS 2005 is, my confusion is what exactly means "no control over your namespace"?
No control over your namespaces. Sure, you can manually add namespaces to pretty much anything, but visual studio will fight you every step of the way. With generated code such as ADO.NET DataSets and such, this gets very hard to control. Eventually you will give up and just let VS put everything in the default namespace. In large applications this gets very annoying, especially if you like a well structured application.
Appreciate if anyone could show a sample here.
Just test this: create a Web Application and a Web Site, then take a look to the namespaces created into the Default.aspx.cs:
WebSite: has no namespace
WebApplication: has namespace
When you have a very big application it's impossible to find your classes without namespaces.
Now create a DataSet:
WebSite: no .Designer.cs created -> namespace will be created automatically on the fly
WebApplication: .Desinger.cs created with proper namespace.
George, Web Sites are not specific to VSTS. That's a normal Visual Studio feature, haunting us since Visual Studio 2005.
Also, see https://stackoverflow.com/questions/237664/web-site-vs-asp-net-web-application-in-visual-studio.