Our application is in Dotnetnuke 4.9.2 version,
In our recent security audit they found that in file DNN.js it sets some cookies in SetCookie method,
I need some info on why DNN.js uses this file for ?
Can I comment this out, if so what would be the complications >
Any references would be helpful
Thanks
You should really upgrade to a newer version of DotNetNuke as there are a lot of security issues that have been resolved in the 4 or 5 years since DNN 4 was last released.
The cookies are likely setting things like "Visibility" on modules that can be expanded or collapsed, or setting cookies for if you have the Control Panel in View/Edit/Layout mode
Related
I am preparing a WPF app to be released, I have about 5 modules (Class Libraries) along with the main app (Windows Application), should I change all the modules and the application build configurations from Debug mode to Release mode? or is it enough to only change the Main App build configuration mode to Release?
Toolbar
You can refer to the toolbar and select specific configuration for the current solution. It will automatically change building configuration for the all projects included in the solution itself (in spite of any dependencies between projects).
In case if you cant see the configuration combobox in toolbar, try to add it using the Standard Toolbar Options button.
Configuration Manager
Used for detailed building configuration management. Change configuration and platform options here both for one single project or the whole solution.
Menu bar/Build/Configuration Manager
Security
Unfortunately or not, but there is no solution to ensure the complete security of the application. We can combine a bunch of different techniques, but thats still not secure enough.
Please refer to first, second answers of this question to get details.
Change all to Release with the main app as well and build. There is no reason to have debug code, for size and security, in released software.
Apparently, the ExtJS' forum isn't working anymore, so asking the question here.
I am trying to upgrade ExtJS integrated in a big application. Currently, it's using version 3.4.1 and I have to upgrade it to 7.5.0, so a lot of changes are expected. It's my first time working with ExtJS. I've been reading their documentation & examples for a while now, but I'm having issues understanding some things.
If someone's experienced with ExtJS, could you tell how big is the difference between these versions? What kind of effort is expected for this upgrade? Will I have to rewrite everything, or just changing files and API calls would be enough?
Another thing is that the folder structure in the new version looks quite different from the older version. Ours using 3.4.1 looks like this -
ext-js 3.4.1 image
There are no new adapter or resources folders in the new verion. Are these folders not required anymore, or is it possible to get the same folder structure with the new version?
Is it possible to download older versions of ExtJS like 4.x, 5.x etc.? I tried but couldn't find it, I was able to download the older documentation though.
Downloaded the latest ExtJS version from here.
Referring this Sencha ExtJS documentation.
Any help would be appreciated. Thanks in advance.
Download
You should download the version from support.sencha.com. There you can find all versions.
To access the download page, you need to log in. If you have lost your login, you can contact Sencha's licensing department.
Make sure you have a valid license.
Upgrade
If you are new to Sencha, you should not do the work yourself. Between version 3 and 7, there are at least two new coding paradigms and you'll have to rewrite everything. Unfortunately, there is no easy upgrade process from 3 to 7. If you had to upgrade from 5 to 7, it would be possible to ignore all the cool new features, but if you are starting from 3, you will have to rewrite everything.
Building process
In your screenshot, I can see that you are using the full ExtJS file. But are you really building the application? That means you end up with a single js file and a single css file.
Are you building your application?
Are you using SCSS?
You should definitely contact someone with experience. I've done quite a few upgrades in ExtJS to know that you need help with this.
I have a project that was last run earlier this year. I've installed latest netbean with plugin but get the following when I start the app.
java.io.UTFDataFormatException: malformed input around byte 200
at java.io.DataInputStream.readUTF(DataInputStream.java:656)
at java.io.DataInputStream.readUTF(DataInputStream.java:564)
at com.codename1.ui.util.Resources.loadTheme(Resources.java:1270)
at com.codename1.ui.util.Resources.openFileImpl(Resources.java:303)
at com.codename1.ui.util.Resources.openFile(Resources.java:269)
at com.codename1.ui.util.Resources.<init>(Resources.java:189)
at com.codename1.ui.util.Resources.open(Resources.java:768)
at com.codename1.ui.util.Resources.open(Resources.java:688)
at com.codename1.impl.javase.JavaSEPort$4.run(JavaSEPort.java:1720)
at com.codename1.ui.Display.processSerialCalls(Display.java:1056)
at com.codename1.ui.Display.mainEDTLoop(Display.java:873)
at com.codename1.ui.RunnableWrapper.run(RunnableWrapper.java:120)
at com.codename1.impl.CodenameOneThread.run(CodenameOneThread.java:176)
I did create a sample app that worked and noticed that the properties tab shows it as a Gui Builder Project. My older project does not show this. I have tried comparing the properties but I do not see what is determining this.
I also copied the theme and the sample code into my project, used that as the main class. The problem still persists.
Any help would be appreciated.
Thank you
Sam
We updated the format of the resource files so newer skin updates might collide with this project. If you use Update Client Libs it should work fine.
However, this change might also cause issues with newer skins if you are using versioned builds. Since the skin includes the native device theme within and we updated the theme file builtin the skin. You can understand our motivation for this change by looking at the before/after screenshots in our 3.8 release announcement.
As a workaround for that problem you can switch a skin and download an older version of a device skin from our skins project. You can then add that skin manually and use that.
My VS2010 doesn't stop at breakpoints inside of silverlight application. It appears that no symbols for it have been loaded during debugging. When I hover over the break point it says "The braekpoint will not currently be hit, no symbols have been loaded".
I have tried all of possible solutions offered by google and have no success. The problem occurs even when I create brand new silverlight app hosted by an ASP .NET web project. All of my project configuration looks fine - silverlight debugging is enabled in the Web project.
I am using silverlight 4.
here a link to the sample project created out from the tepmlate.
Any thoughts ?
P.S I just tried to reinstall VS2010 and the problem still exists.
EDIT: I just tested the same project on another machine and it stops at the break point it seams that the problem is somewhere in the configuration of VS or silverlight.
with Matt Dotson's help I managed to attach the debugger manually. However this solution is not good enough for daily use.
Depending on my experience in Silverlight following these steps keep your project debug-gable.
Condition 1>
Firstly we need to be ensure that in Web Project's properties there is a Web section, as you see below Silverlight checkbox must be checked.
Condition 2>
Follow In Menu Debug => Attach Debugger>
Visual Studio sometimes can't attach debugging platform you need to lead the way :) . By this way you may debug other platforms,(also you may debug your product platform but pdb files must be sync and don't forget you may suspend your product platform using this).
Condition 3> Your default web browser may be Firefox,Chrome or other than IE.By Visual Studio default try to attach to IE. But when you run VS calls default browser,so you need to have a manual attachment in Condition 2 or set your default browser by right clicking on default page > Browse with .
Condition 4> There is xap file generally located in web project\ClientBin directory. Sometimes after build operations this file can't be replaced and your ProjectDll and your Project PDB files not be sync. This cause wrong line match while debugging or can't find a debugging file attached caution. I strongly suggest delete all generated files in Bus project and delete Clientbin\ProjectName.xap file. After rebuild all it must be ok!
Hope helps.
What broswer are you using? You need to be using Internet Explorer to debug silverlight projects.
I have had a similar frustrating experience with this but in my case the solution was very simple. It seems that somehow, and I really have no idea how, the debugger option for Silverlight had become unchecked in the properties on the hosting ASP.NET project.
I just assumed that as I had been previously debugging, this option was set and I didn't bother to make sure that this was this case. Just goes to show that one should always check the basics first; if I had done that it would have saved me some time.
To check this in VS2010, right-click on the project and select properties, change to the Web tab and check the Silverlight option at the bottom of the page, in the debuggers section.
Also see the debugger to a silverlight process
http://msdn.microsoft.com/en-us/library/cc838267(VS.95).aspx
If that doesn't work, then
reset iis (if you are debugging in that)
delete temporary asp.net files (%SystemRoot%\Microsoft.NET\Framework\versionNumber\Temporary ASP.NET Files)
clean and rebuild your solution
The resolution came after 2 days of headbanging. It appears that the link which Malcolm gave covers exactly my problem but my I was narrow-minded enough not to pay it enough attention because when I run the debugger as long with the app my default browser was FF. So I thought that after the FF starts I can load the page from IE or Chrome.
Actually the problem is that the debugger cannot be attached to the silverlight project because of the FF. And when I load the app from IE or Chrome the debugger dis still not attached.
Thanks to everyone that tried to help.
if you have multiple project, Rebuild the project separately that you want break point. Its work for me
Try also picking internet explorer from browser list menu as your browser
I'm new to Silverlight and am curious how a Silverlight application is updated from one version to the next. Is ClickOnce used to do this, or are there other, hopefully transparent simple and reliable, ways of doing it?
If using a standard Silverlight application (not out of browser), your regular HTTP rules are respected. So assuming caching is sensible, the latest version will be downloaded from the server automatically when the page is launched.
As for when it is running out of browser, Tim Heuer has a good blog post outlining it:
http://timheuer.com/blog/archive/2009/03/18/silverlight-3-offline-update-framework.aspx
Basically, a programmer can request for updates from the server and have the application update itself if necessary.