|
gscheek wrote: will not compile
and what does that mean?
|
|
|
|
|
When trying to compile the solution, it contains 1000+ errors. VS2008 compiles fine with no errors.
GSC
|
|
|
|
|
really? that is horrible. I haven't been playing with VS2010 myself but that is not the behavior I expect, nor what I gathered from reading lots of posts in the Visual Studio forum and Lounge.
Do you have .NET 2.0 installed? (yes the Framework itself, not VS2008).
|
|
|
|
|
I've converted many projects from VS2008 to VS2010 and have not had any issues. Are they warnings or errors? What some of the errors you are experiencing?
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
gscheek wrote: but will not compile with VS2010, because of the mixed frameworks
That really should not be the case.
When you opened the solution in 2010, did the conversion happen correctly?
|
|
|
|
|
When converting from 2005 - VS2008, it worked fine. But when converting the 2005 solution to VS2010, there was a warning for each project. The warning message was that the project is targeting 2.0 framework, but contained references to 3.0 .net dll's. If VS2008 didn't have an issue with this, why would VS2010.
Also, I have VS2005, VS2008, and VS2010 installed on the same machine.
Exact warning message from VS2010, it done this for several of the projects in the solution file.
Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
GSC
modified on Thursday, April 29, 2010 10:08 AM
|
|
|
|
|
gscheek wrote: Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
Did you try this?
|
|
|
|
|
yes,
I was trying avoid doing this though, since in VS 2008 it worked when I targeted the 2.0 framework. After I changed all the projects to 3.5 framework, many of the errors disappeared, but now other ones have come up. So I'm trying to get those fixed.
GSC
|
|
|
|
|
Hi all,
I'm excited to inform you that CodeFort with its release last week broke the barrier and became the first .NET obfuscator to support renaming of identifiers in XAML and BAML code. This is a huge step forward in .NET obfuscation technology, because it removes the need to manually exclude all the Presentation Layer properties and types from obfuscation, as you need to with most obfuscation tools today. Of course it will mean a great improvement in security in terms of protecting your intellectual property rights from attackers.
CodeFort also comes with a range of powerful protection features such as Reference Scrambling and Anti-Tampering, making it a state-of-the-art protection tool. Reference Scrambling decouples the link between calls to external methods, and the reference to those methods, making it impossible for an attacker to browse through IL or disassembled code, because the method calls are pointing to unusable locations.
Check out the free version if you're interested - we are very much looking forward to your feedback!
CodeFort Free Edition
Best regards,
Christian
email: support (.) creatix.dk
modified on Wednesday, April 28, 2010 7:36 AM
|
|
|
|
|
Post it as News or as General (like information - Message Type).
Please don't post News or Information like Question.
Jinal Desai
|
|
|
|
|
Hi Jinal,
Thanks for your hint. I have corrected it now.
Best Regards,
Christian
|
|
|
|
|
I have done VB.net application by the functionalities of export the word documet. Its working fine in the developemnt machine. During the developemnt , i have added the MICROSOFT.OFFIVE.WORD.INTEROP is added.
I need to install in the clinet machine. How to make a setup with this com refrence file.
I need some hurry. Plz help me.
Thanks
|
|
|
|
|
Member 4619061 wrote: I need some hurry.
Another way to say urgent 
Don't ask for urgent help, it is rude. We are all here voluntarily and although it may be urgent to you it not to anyone else.
Member 4619061 wrote: How to make a setup with this com refrence file.
It's not a COM reference, it's an assembly. That should give you an idea.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Thanks for yr quick reply.
I dont have much exp in setup creation. I lloked out google and got some idea. but i dont findout how to add assemblies and DB in the setup?
Plz help me
|
|
|
|
|
|
Create setup project.
Add .exe file of your project, it will automatically add all the dependency
dlls and references.
If it will not include com reference (MICROSOFT.OFFIVE.WORD.INTEROP)
then you can add it manually by adding file to your setup project.
That's it.
Jinal Desai
|
|
|
|
|
|
I have an application in which is made in .NEt 2008 in c#.
I want to set up wizard for this application.
I am faceing litle problem to make it.
I want to check some prerequisite in the client machine while installing this project.If this prerequisite does not evaluated true the installation program will be automaticaly stoped with throwing proper error message.
For my application prerequistes in client machine are
1. AutoCAD 2008 or higher version
2. .Net framework for 2008 or higher version
3. windos XP,windows 2000
Can any one guide me how to check these 3 prerequisite in client machine
with regards
|
|
|
|
|
|
Hi. I have installed .NET Framework 4.0 in my computer.
I have created 3 .NET Applications of versions 2.0, 3.5 and 4.0. When I tried to run all three, only the 4.0 version ran successfully, the other two(2.0 and 3.5) show an error.
Does this mean, for a computer without .NET framework installed, that I have to install the .NET Framework 2.0 and 3.5 and not just 4.0?
Thanks.
|
|
|
|
|
Rue Leonheart wrote: install the .NET Framework 2.0 and 3.5 and not just 4.0
Have a look at the Application Compatibility section here.
You need to specify the supportedruntime version in a config file.
|
|
|
|
|
What config file, original one or the application config file. It can't run programs older than version 4.0.
Do you mean, I have to recompile those older programs to target 4.0? What if I'm not the one who made those programs?
|
|
|
|
|
If you are running an exe called myApp.exe, you will need to create an application config file called myApp.exe.config. This config file will then contain the supportedruntime tag.
For more information on the supportedruntime tag see here. For information on configuration file schemas see here.
|
|
|
|
|
So even if I'm not the one who made the exe, all I need to do is make the config file with the same name? Do I need to put it on the same folder as the exe. Thanks a lot.
|
|
|
|
|
Yes, the config file should have the same name, and it should be in the same folder.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
