You searched for the word(s): userid:714969

More Search Options

RSS Available

• CSS intellisense problem

  I am having an issue with intellisense regarding how its validating my ascx controls. Here is the issue, an ascx control obviously inherits the CSS of the aspx page it is inserted into, but since VS doesn't know where it goes, it just figures every single CSS class is invalid. Well, the classes exist, everything works, I just have an absurd amount of invalid warnings that I can't get rid of because VS is complaining about something it can't even see anyway. How do i fix this? When I say

  Posted to Visual Studio 2008 (Forum) by jbardrof on 10/30/2008

• Re: Visual Studio 2008 install freezes windows XP

  Just another thank you! I was dumbfounded as to why I couldn't get this to install on my R61. Thanks so much!

  Posted to Visual Studio 2008 (Forum) by jbardrof on 9/15/2008

• Re: Hosting MVC Application on localhost

  I'm guessing you are using IIS 6? if so, go to your global.asax page and change your route to: {controller}.mvc/{action}/{id} If that is not the problem please give more details as to what version of IIS you are using, and what steps you took to deploy your site.

  Posted to ASP.NET MVC (Forum) by jbardrof on 7/15/2008

• Re: Dundas Chart and MVC Framework Errors

  you can save A LOT of hassle by just using the routing library with a regular Webforms website. You'll have much fewer issues, and still get to use routing.

  Posted to ASP.NET MVC (Forum) by jbardrof on 7/9/2008

• Re: Forcing a page refresh?

  Actually you don't want a page refresh at all, what you want is to tell jQuery to load the response from your action (meaning it should return to the view rather than refresh the original action. Then the return value from ajax can then simply be added to your select box, all in jQuery. The benefit here is that rather than an entire page refresh, you are simplifiying, and minimizing the work and traffic required. If you are not sure how to accomplish this, post some of your code and I can help

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/20/2008

• Re: MVC & VS 2005 .NET 2.0

  [quote user="TNE"] Developing in MVC should be no different, or actually better. Your programmers should be handing off data to the view, and the designers should be displaying the data. Your programmers should not be responsible for UI. [/quote] True, IF you have the resources to do that, some places the designers and the developers are the same people. If you are lucky enough to be able to separate the concerns amongst your resources then the ability to allow developers to simply write

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/19/2008

• Re: MVC & VS 2005 .NET 2.0

  That is true, of course, from a pure front end web designers perspective, that was always a terrible way to develop. The amount of superflous html created was a mess. The sell should be that your webpages will be tighter, more concise, and you'll have better control over the outputted html. This making your pages faster, cleaner and even sometimes the holy grail of "SEO friendly".

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/19/2008

• Re: MVC & VS 2005 .NET 2.0

  Not dealing with webforms should be the best part of the sell! At least around these parts, many of us are not very fond of the webforms model. It does take some getting used to, but for me personally, after getting into the MVC I really dislike the webforms model now, the MVC is so much cleaner, so much more concise with what you are trying to do, and so much less fluff along the way.

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/19/2008

• Re: Where do I put "Save" method and code?

  If by save you mean the logic to commit it to your datastore, then the repository would be a good place. Repositories generally serve the purpose for object lifecycle, and save is a part of its lifecycle.

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/18/2008

• Re: MVC & VS 2005 .NET 2.0

  this will give you the templates: http://staff.southworks.net/blogs/matiaswoloski/archive/2007/12/11/ASP.NET-MVC-Visual-Studio-2005-Template.aspx Now, you do need to get .NET 3.5 as things like Url.Routing are in the newest framework and necessary for the MVC to work. Now if you cannot use 3.5 and must use 2.0 then unfortunately the MVC won't work.

  Posted to ASP.NET MVC (Forum) by jbardrof on 6/18/2008