|
I have C++ code which has calls like this
1) SystemTimeToFileTime(&st, &m_Time)
Before above call st is assembled by assigning values to its members manually - but only year, month, day, hour, minutes and seconds are assigned to it.
m_Time is instance variable of type FILETIME.
Afterwards there is a function like that:
2) dppDatetime_t RsDateTime::GetAsPrepaidTime() const
{
dppDatetime_t dt;
SYSTEMTIME st = GetLocalTimeAsSystem();
dt.Year = st.wYear;
dt.Month = st.wMonth;
dt.Day = st.wDay;
dt.Hour = st.wHour;
dt.Minute = st.wMinute;
dt.Second = st.wSecond;
return dt;
}
GetLocalTimeAsSystem defined as:
3) SYSTEMTIME RsDateTime::GetLocalTimeAsSystem() const
{
SYSTEMTIME st;
::FileTimeToSystemTime(&m_Time, &st);
return st;
}
I basically need to replicate all this functionality I mentioned in above 1), 2), 3) points in C#. I would really appreciate some help on how to go with this? How to achieve same result in C#?
Can't I implement what is done above using only DateTime structure in C#?
modified 30-Oct-15 4:46am.
|
|
|
|
|
I really don't understand what you want. C++ has a lot of ugly structures for dealing with time, and in c# you don't have to care - you have the very-easy-to-use DateTime class.
For getting the current time, just use
DateTime.Now
DateTime.UtcNow
Best,
John
|
|
|
|
|
I want to achieve steps 1 and 2 as in the question
|
|
|
|
|
they make no sense in c#
Best,
John
|
|
|
|
|
This is essentially the same question as the one below. If you need to use one of the Win32 calls and returned structures then you need to use PInvoke. I gave you the links already.
|
|
|
|
|
If you look at my question carefully you can see I think I don't need PInvoke and I can achieve all with DateTime. That is why I asked
|
|
|
|
|
Achieve what? Your question is not clear.
|
|
|
|
|
I want to achieve in C#, same what this code achieves in C++. Is this possible? How? Preferable would be without using PInvoke
void CVersion::GetVersion(DWORD *v1, DWORD *v2, DWORD *v3, DWORD *Build) const
{
char Path[1024] ;
DWORD Len1, Len2 ;
VS_FIXEDFILEINFO *FileVerInf ;
if(GetModuleFileName(m_hModule, Path, 1024))
{
if((Len1 = GetFileVersionInfoSize(Path, &Len2)) != 0)
{
BYTE *InfoBlob = NULL ;
try
{
LPSTR lpstrVffInfo ;
UINT uVersionLen ;
InfoBlob = new BYTE[Len1+255] ;
if(!InfoBlob) throw -1 ;
lpstrVffInfo = (LPSTR)InfoBlob ;
GetFileVersionInfo(Path, Len2, Len1, lpstrVffInfo) ;
BOOL bRetCode = VerQueryValue((LPVOID)lpstrVffInfo,
(LPSTR)"\\",
(LPVOID *)&FileVerInf,
(UINT *)&uVersionLen);
if(!bRetCode)
{
FileVerInf->dwFileVersionLS = 0 ;
FileVerInf->dwFileVersionMS = 0 ;
}
if(v1 != NULL) *v1 = (FileVerInf->dwFileVersionMS&0xffff0000)>>16 ;
if(v2 != NULL) *v2 = FileVerInf->dwFileVersionMS&0x0000ffff ;
if(v3 != NULL) *v3 = (FileVerInf->dwFileVersionLS&0xffff0000)>>16 ;
if(Build != NULL) *Build = FileVerInf->dwFileVersionLS&0x0000ffff ;
} catch (...) {;}
if(InfoBlob != NULL) delete[] InfoBlob ;
}
}
}
If it is not possible without Pinvoke, can you show me some sample how to do this with PInvoke?
|
|
|
|
|
If you do not want to use PInvoke directly you could use a C++ DLL to return the information in a suitable format. See also P/Invoke tutorial[^].
|
|
|
|
|
Would you be kind to show me how to achieve similar with PInvoke? I am beginner with .NET
|
|
|
|
|
Go to the link I provided and follow the tutorial, although P/Invoke is somewhat advanced for a beginner. You can also find more useful information on The PInvoke website[^].
|
|
|
|
|
This is why I am saying it seems a bit advanced for me. This is how I have reached so far with bit of googling, maybe you can help further?
[System.Runtime.InteropServices.DllImport("coredll")]
private static extern bool GetFileVersionInfo(string filename, UInt32 handle, UInt32 len, IntPtr buffer);
[System.Runtime.InteropServices.DllImport("coredll")]
private static extern UInt32 GetFileVersionInfoSize(string filename, out UInt32 handle);
[System.Runtime.InteropServices.DllImport("coredll")]
private static extern bool VerQueryValue(IntPtr buffer, string subblock, out IntPtr blockbuffer, out int len);
UInt32 msb = (UInt32)System.Runtime.InteropServices.Marshal.ReadInt32(verbuffer, 8);
UInt32 lsb = (UInt32)System.Runtime.InteropServices.Marshal.ReadInt32(verbuffer, 12);
major = (msb & 0xFFFF0000) >> 16;
minor = (msb & 0x0000FFFF);
build = (lsb & 0xFFFF0000) >> 16;
revision = (lsb & 0x0000FFFF);
But I don't know what is verbuffer?
|
|
|
|
|
You need to allocate the version info structure as described on MSDN. You then need to make the calls to the various routines (not just declare them) via the pinvoke calls in order to get the structure filled in with the information.
|
|
|
|
|
what about my other approach - see comment below. It showed similar version with one DLL when I tested
|
|
|
|
|
user20044 wrote: what about my other approach
What about it? You need to test your code and check whether it returns the information you want. If it does not get the correct results, then provide the full details so people can try to help.
|
|
|
|
|
This is my newer approach. Do you think this is fine?
var versInfo = FileVersionInfo.GetVersionInfo(dllPath);
return String.Format("{0}.{1}.{2}.{3}", versInfo.FileMajorPart, versInfo.FileMinorPart, versInfo.FileBuildPart, versInfo.FilePrivatePart);
|
|
|
|
|
Are you trying to get the assembly version?
If so, then it's trivial in C#:
string version = Assembly.GetExecutingAssembly().GetName().Version.ToString();
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
My code will run inside DLL, and this needs to get probably(I am not sure) version of DLL
|
|
|
|
|
Try it: That's what GetExecutingAssembly does - returns the DLL if the code is in a DLL, and the EXE if it's still in the original app assembly.
There is another methods to get the EXE directly: Assembly.GetEntryAssembly[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You can see my approach in response above to Richard, any comments?
var versInfo = FileVersionInfo.GetVersionInfo(dllPath);
return String.Format("{0}.{1}.{2}.{3}", versInfo.FileMajorPart, versInfo.FileMinorPart, versInfo.FileBuildPart, versInfo.FilePrivatePart);
modified 29-Oct-15 9:06am.
|
|
|
|
|
There is File version info and Assembly version info. The two are not the same.
The question is which one are you really looking for.
|
|
|
|
|
The one I am looking for is which is used in C++ code I showed
|
|
|
|
|
I have one app which freezes UI on StartWipeFile() function call..How to solve problem????plz help
try
{
var result = MsgBox.MsgGridVisbility("Alert",
"Do you want to continue for disk wipe ?", 2,
Config.MsgBoxFontColor, Config.MsgBoxHeaderBgColor, Config.MsgBoxHighlightedBtnColor,
Config.MsgBoxNormalBtnColor);
if (!result.Equals("2"))
{
BusyBar.IsBusy = false;
return;
}
this.Dispatcher.Invoke(DispatcherPriority.Normal, (ThreadStart)delegate
{
BusyBar.IsBusy = true;
StartWipeFile();
});
}
finally
{
BusyBar.IsBusy = false;
}
}
private void StartWipeFile()
{
try
{
CreateFile(drivelist.SelectedValue.ToString());
wipe.WipeFile(fileName, Convert.ToInt32(Regex.Match(passlist.SelectedValue.ToString(), @"\d+").Value));
}
catch (Exception)
{
BusyBar.IsBusy = false;
}
finally
{
BusyBar.IsBusy = false;
}
}
public void CreateFile(string DriveNameSelectedValue)
{
try
{
char p = Convert.ToChar(DriveNameSelectedValue.Remove(1, 2).Cast<char>());
DriveManager.FormatDrive(p, "New Folder");
var disksize =
Convert.ToDouble(String.Format("{0 .00}",
AvailableFreeSpaceFormatted(DriveNameSelectedValue, DiskSizeUnit.Bytes)));
//var data = ConvertGigabytesTobytes(Convert.ToDouble(memorytxt.Text));
//var data = ConvertGigabytesTobytes(Convert.ToDouble(AvailableFreeSpaceFormatted(drivelist.SelectedItem.ToString(), DiskSizeUnit.GigaBytes)));
//string fileName = @"D:\\Text.txt";
fileName = @"" + DriveNameSelectedValue + "WXF1ENCR.txt";
if (File.Exists(fileName))
{
File.Delete(fileName);
}
var fs = new FileStream(fileName, FileMode.CreateNew);
// Create the writer for data.
var w = new BinaryWriter(fs);
// Write data to Test.data.
try
{
for (int i = 0; i < disksize; i++)
{
w.Write((byte) i);
}
}
catch (IOException)
{
//w.Close();
//fs.Close();
//return fileName;
//return Convert.ToString(0);
}
//w.Flush();
w.Close();
//fs.Flush();
fs.Close();
//return fileName;
}
catch (Exception ex)
{
MessageBox.Show((ex.Message));
}
}
|
|
|
|
|
If it's freezing the UI, then it's probably because the file wipe is taking a considerable amount of time - and because it's all being done in the same thread, the UI can't update until the long running task is complete.
Move your Wipe into a different thread and it should "unfreeze" the UI. Have a look at the BackgroundWorker class[^] - it's easy to use and provides event for progress reportign and task completion.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
1. You need to call StartWipeFile() on a different thread.
2. When posting, check that you don't mis-paste the code - such as showing & quot; etc.
3. Do a little debugging yourself - just clicking the "Break into debug" would have shown you the problem
Best,
John
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
