AtmoWin - improvement discussion (1 Viewer)

B

BassFan

Guest
@azzuro PS : What do you think to move Atmowin folder in "Programdata/Atmowin" or "PData/Team MP/Atmowin" directly ?
better to "Programdata/Atmowin" then AtmoWin do nothing with MP.. ;)
can Change then later.

greets
 
B

BassFan

Guest
Thanks..
@azzuro ok is nothing what i should do .. all removed after finish with XML
------------------------
here are a TestBuild nothing special

only used for this time Standard Profile.
please Test.
  • 1. If create XML successful on start (if not exist)
  • 2. All Option to default after Change any and delete the XML then?
  • 3. Work read and write do the XML without any Problem ?
  • 4. work the file after delete the registry entry? (please make a update before)

and so on.

greets
 

azzuro

Test Group
  • Team MediaPortal
  • May 10, 2007
    9,984
    5,663
    France - IDF
    Home Country
    France France
    @BassFan
    can you release this file with Release mode, because i try to test ( on friend computer), without Visual studio installed. and i have message error, with MSVCP110d.dll missing ..

    From http://social.msdn.microsoft.com/Fo...3bb/msvcp100ddll-is-missing?forum=Vsexpressvc
    Came across similar problem recently. The strangest thing that my resulting DLL was dependent upon MSVCR100.dll (without 'D'), which was right because I changed /MDd to /MD, but also dependent upon MSVCP100D.dll, which did not seem right for the same reason. After long investigation I found that it depends upon preprocessor definitions. Changing _DEBUG to DEBUG solved the problem for me..
     
    B

    BassFan

    Guest
    @BassFan
    can you release this file with Release mode, because i try to test ( on friend computer), without Visual studio installed. and i have message error, with MSVCP110d.dll missing ..

    From http://social.msdn.microsoft.com/Fo...3bb/msvcp100ddll-is-missing?forum=Vsexpressvc
    Came across similar problem recently. The strangest thing that my resulting DLL was dependent upon MSVCR100.dll (without 'D'), which was right because I changed /MDd to /MD, but also dependent upon MSVCP100D.dll, which did not seem right for the same reason. After long investigation I found that it depends upon preprocessor definitions. Changing _DEBUG to DEBUG solved the problem for me..

    that should be.. hmmm

    greets
     

    Users who are viewing this thread

    Top Bottom