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

More Search Options

RSS Available

• skin/container thumbnails not rendering properly

  system config: DNN 3.0.12 SQL SVR 200 sp3a Win XPP & W2K3 admin rights to both platforms .NET 1.1 When I install a clean copy of 3.0.12 on either platform, then access the skins/container module, all of the available options (skin type and containers) thumbnail graphics display as broken graphic icons. I'm assuming that they are to render a smaller version of what the skin/container would look like for real? While they do not display correctly, they do 'apply' correctly. Does anyone have an idea

  Posted to DotNetNuke (Forum) by meistvan on 3/20/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  Enough everyone, please. I had a issue, that I was looking for resolution, but you all except for a two people have decided to continue what you say I was doing, flaming. Maybe my definition is different, but that was not my intent. I'm sorry that to see that others would spend more time attacking me vs. the problem raised. In six months, I'll be in production. By then v 2.0 should be stable and fully functioning. I need to plan ahead and was hoping for some help. Obviously, this group (top 50 types

  Posted to DotNetNuke (Forum) by meistvan on 3/20/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  I really appreciate this response. While I have both VS 2003/2005, I've made no attempt to recompile to research the problem beyond what I've done. That was not my intent in using DNN (any version) or ASP.NET (any version). I simply have been trying to create a stable environment from which to focus on my application development. If I guess wrong in my tool set, and develop bad code, people will die (no kidding, this is for real!!). My choices will be reflected in a host of other parallel develop

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  Fine with me. Could someone at least spend a little time to confirm what I've run into or is not that much of interest since its 'beta'? Seems books are coming out, people are plugging the modules, components, etc on something that is 'beta'? I just wanted a confirmation to the core issue ' something that was working fine in a past version is now not working when moving to the new, albeit beta platform' My stuff is not production. I'm in design, testing, trying out mode right now. My shcedule is

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  I've done that. I currently have .NET 2.0 running with 2.1.2 and both are functioning as developed. try this scenario: 1 - add an Test/HTML module (3.0.12) and place some content within it. (under 1.1). should be able to 2 - also, try to add users (3.0.12) under 1.1, should be fine now... 3 - install .NET 2.0 and try the above. a - you can;t edit the test you just did under 1.1 in the T/H module. In fact, you can even have the cursor active within it. b - you can't successfully add users to the portal

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  Everyone I really appreicate your concerns, issues, etc. I've obviously touched a nerve, so be it. For that, sorry. I 'did' post something like that and did try to search for issues along the same lines. Did not find anyting that could have helped, thus me 'really, I was not not trying to flame' email. I needed an answer, and from past posts, most have been ignored. BTW, has anyone place a $$ value for this product? Currently, my customer is comparing it to a commerical product that cost $560,000

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  what 'foul language'? I just expected that sine this product has such a large following, and so many revisions, it would follow that what was working in the past would still work. I've posted simple, tone-less stuff in the past to no avail. I simply needed to understand why something that was working in 2.1.2 now does not in 3.0.12? Did 2.0 change so much, and is DNN really not that 'open source' that the two issues cancel each other out? Come guys. As someone on this thread has already said, 'get

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  think like that, and you'lll never get ahead. you must get you head out of the hole it in, and realize that one must think 3-6-9 months into the future in todays fast changing world. I do not know nor really care to know what 'carrer' you have, but I've been at mine probably before you were born. So please don't preach to me about job paths. Get laid off a few time, thru no fault of you own, write software that has life and death issues attached to it, then come to me as an equal. I use tools like

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  the problem was in a simple, core function. I shiver to think what else might not work as several version ago. I can work around the harder ones. I was just surprised that a simple function like editing test/html, or adding a user account to the system failed. maybe this is not a 'open source' as its being announched to be? 2.1.2 worked, but I really like ehat the core team did with 3.0.12 and was prepared to give them a forum and visibility for their product, work, etc that they could never have

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005

• Re: Problem with 3.0.12 and .NET 2.0 Beta - CORE TEAM FIX!!!

  excuse me, junior, I kow that vlaue of work, and the monies that come with it. deploying a product, whether for $$ or free, does not mean taking steps back in standard, core, working functionality. Then again, you're probably not old enough to understand what it means to deploy a product that has real requirements, works as designed, planned, and announced. I find that most of the 'younger' developers, which I'm assuming you are (if wrong, then sad for you) have not learned the proper methods for

  Posted to DotNetNuke (Forum) by meistvan on 3/19/2005